Yes, that was the problem. Thank you very much for solving it for me.
on 7/17/11 4:27 AM, Peter Hosey <[email protected]> wrote: > Thinking some more about this, I figured out the problem. > > It's your script. > > Your script and Dialectic both register under the same application name, but > with different notifications. Since Growl treats scripts the same as > applications, it sees this as Dialectic re-registering with a different set of > notifications, and assumes that Dialectic no longer supports the notifications > it had previously registered with (after all, ³Dialectic² just registered > without them), so it deletes them. > > That's why your settings get lost, and why the Growl preference pane shows a > different set of notifications from what your script registered with‹it's > showing what Dialectic registered with. If you cause your script to fire, then > go back to the Growl preference pane, you'll find that Dialectic's list of > notifications will have changed to one item, which is ³incomingCall². > > There are two or three solutions: > > 1. Change your script's application name to something else so as not to > conflict with the real Dialectic's registration. > 2. Change your lists of notifications to match Dialectic's. (Fragile.) > 3. If possible, use Dialectic's built-in Growl support (such as it is) instead > of your own custom script. -- 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.
