On Aug 30, 2008, at 14:30:52, jeeves.d wrote: > in light of the apparent opposition to letting the application set > the "lifetime" > I don't understand why Growl has an "application decides" option in > the "notification editor"
The default, if neither the application nor the user says whether the notification is sticky, is that it isn't sticky. If the application says it's sticky, and the user leaves it set to “Application Decides”, then it's sticky, because the application said so. If the user sets it to “yes” or “no”, then it doesn't matter what the application says, if anything: the user's order takes precedence. > but, maybe you could simplify your code by not using that option, > having the user set the options in the "notification editor" instead, For every notification? No. Nobody wants to configure every notification from every application; that's what default values are for. The default is non-sticky, which works fine most of the time. If the user wants to change this, they can. > and always sending a GROWL_NOTIFICATION_IDENTIFIER ? What? That has nothing to do with stickiness; it's for coalescing. Moreover, the user doesn't send the identifier; the application does. It's not up to us whether there's an identifier or not. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
