On Sun, May 8, 2011 at 11:47 PM, Paul Traylor <[email protected]>wrote:
> On Sun, May 8, 2011 at 5:17 PM, Peter Hosey <[email protected]> wrote: > > Generically speaking, that implies a bug in the application: Each time, > it registers once with no notifications, then again with its set of > notifications. > > On Sun, May 8, 2011 at 8:47 PM, ylluminate <[email protected]> wrote: > > Well it must then be some sort of an application error. It has > > happened in both Autotest and Guard now. I've changed the settings on > > the "Application Settings" tab as well as the "Notifications" for the > > Display Style and neither will "stick." Guard does not appear to have > > the same problem of resetting back to another app when you back out to > > the list. Interesting stuff, but I can't seem to track things down > > any further than this and I wonder if we're not talking about > > different issues here. > > > > Assuming that the autotest you are refering to is this one > https://github.com/svoop/autotest-growl it looks like internally it > uses the growlnotify binary internally > https://github.com/svoop/autotest-growl/blob/master/growl/growlnotify > ( http://growl.info/extras.php#growlnotify ) which I seem to recall, > re-registers each time it is run which would cancel out your custom > settings. > > We don't recommend that app developers use growlnotify. Some do, but they run into issues like this if memory serves correctly. 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.
