On Aug 4, 10:33 am, Peter Hosey <[email protected]> wrote: > On Aug 4, 2010, at 10:26:01, Jason Wehmhoener wrote: > > > I have a use case that would be well supported by allowing the user to > > choose between multiple actions from within a Growl notification (a > > notification that includes multiple buttons/icons, each calling a different > > callback). ... > > Yes, but Growl's internal architecture and its API do not support this, so > there is no way you could communicate the different actions back to the > application.
this might open up a whole other can of worms, but this type of thing *could* be possible in Growl 2.0 once GNTP support is baked in. the reason i say that is 1) the GNTP spec allows for the Notification- Callback-Context header to be returned with an arbitrary value when the user clicks the notification (so it could be set differently depending on what they clicked), and 2) there are some Twitter- specific displays for Growl for Windows that are doing this very thing: http://www.mageuzi.com/trowl/#displays in his Metro and Twitter displays, there are a few items that can be clicked (replay, retweet, etc). the display sets the GNTP callback headers appropriately for each action and when the sending app is notified of the callback, it can use the different values to change its action accordingly. (in all cases, if the display is used with a sending app that doesnt support those actions, the icons are not even shown in the display). like i said, that might be stretching what Growl was intended for, but since it already allows clicking a notification to trigger an action, it is not too much of a stretch to envision different types of clicks triggering different actions. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
