Comments
-
Greg Hurrell
Yes, this is a good idea. Just to clarify a bit, Synergy doesn't actually know when Growl notifications are "turned on". It basically always sends them and the user either turns them on or off in the Growl preference pane (not the Synergy preference pane). So Synergy doesn't actually have a way of knowing when to send a Growl notification in response to a hot key press and when not.
So a few alternatives are:
1. Add a preference (probably a command-line-only one to avoid clutter in the UI) that the user can use to specify that Growl notifications should be sent.
2. Just send the notifications anyway whenever the hot key is pressed and require the user to deactivate them in the Growl preference pane if he/she doesn't want to see them.
3. Infer whether or not Growl notifications might be on by considering whether the Floater is on (that is, if the user has the Synergy floater on, then assume that they probably have Growl off; and vice versa in the converse case).
4. Add a completely new hot key for popping up a Growl notification (for problems with this approach see bug #294).
-
Michael Martz
(In reply to comment #1)
Yes, this is a good idea. Just to clarify a bit, Synergy doesn't actually know when Growl notifications are "turned on". It basically always sends them and the user either turns them on or off in the Growl preference pane (not the Synergy preference pane). So Synergy doesn't actually have a way of knowing when to send a Growl notification in response to a hot key press and when not.
So a few alternatives are:
1. Add a preference (probably a command-line-only one to avoid clutter in the UI) that the user can use to specify that Growl notifications should be sent.
2. Just send the notifications anyway whenever the hot key is pressed and require the user to deactivate them in the Growl preference pane if he/she doesn't want to see them.
3. Infer whether or not Growl notifications might be on by considering whether the Floater is on (that is, if the user has the Synergy floater on, then assume that they probably have Growl off; and vice versa in the converse case).
4. Add a completely new hot key for popping up a Growl notification (for problems with this approach see bug #294).
I think the most intuitive approach would be to have the hide/show floater hotkey always send growl notifications(#2). If the user has growl notifications enabled, then they are likely to have the floater turned off and vice versa anyway, but perhaps a user would like growl notifications to display their info and the floater to display other information.
-
Greg Hurrell
Changing assignment to reflect my new email address.
https://wincent.dev/a/news/archives/2006/05/change_of_email.php
-
Greg Hurrell
See also:
https://wincent.dev/a/support/forums/showflat.php?Number=1027
Add a comment
Comments are now closed for this issue.