I can think of at least two use cases that getting rid of this pref would potentially break.
In both cases GrowlHelperApp is controlled by launchd. 1) A machine with at least two users one of whom does not want growl notifcations. 2) A user wants to temporarily mute growl for a movie (or presentation). Concentrating on the second use case here is what happens without this pref: User tells launchd to stop GrowlHelperApp and goes to watch their movie. Some app in the background tries to send a notification; this starts GrowlHelperApp to deal with it. GrowlHelperApp checks its prefs and sees that it is suppose to be running and stays on. (at this point growl is already not operating the way the user wants, but lets say that this does not happen until the climax of the movie and the user does not notice) Movie over the user tells launchd to start GrowlHelperApp again. The new copy of GrowlHelperApp upon seeing that there is another GrowlHelperApp running quits; launchd seeing the GrowlHelperApp under its control quiting restarts it (this then begins to repeat in an infinite loop every 10 seconds). User wonders why their resting cpu usage is so high. Use case one is a variation of this with the only difference being that the user has told GrowlHelperApp that they want it off and it quits for that reason instead. On Mar 31, 11:48 am, Christopher Forsythe <[email protected]> wrote: > On Wed, Mar 31, 2010 at 10:38 AM, Peter Hosey <[email protected]> wrote: > > On Mar 31, 2010, at 08:36:26, Christopher Forsythe wrote: > > >> I suppose we could also make a dictionary list to eliminate apps which > >> need to be queried as well, since they are already registered. > > > Good point. We can ignore any bundle that's already registered, which will > > probably be most of them. > > That'd make this a lot less expensive I assume, which I think makes it a > great addition. > > So to recap: > > - Remove the silent mode checkbox and selection in the menu item due to > confusion (Make sure having the preference checked previously doesn't cause > problems would be good for testing). Make it so that GHA only looks for apps > which are not already registered (would that cause problems in case an app > updates and changes the notification list?) > > - Add auto detection logic to look for apps which are currently running on > startup of GHA. > > The second change effectively makes silent mode a duplicate of simply > turning GHA off, so this is removing duplicate functionality. > > Any comments/questions/additions? > > Chris -- 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.
