Ok, I've checked and I don't have "Start Growl at login", so this is the
cause that I don't see GrowlHelperApp running when I've logged in
(obviously).
But, does that means that any user with the same setting will make my
app not show notifications unless I add that growlRegDict?
The explicit registry was to work around this problem that my app and
BeepHammer have, because obviously GHA is not being launched after
registration.
On 24/02/2011 15:42, Peter Hosey wrote:
On Feb 24, 2011, at 00:02:36, Arcnor wrote:
I've noticed, though, that even when notifications are not displayed at all
(GrowlHelperApp is not launched), the following is logged in Console:
24/02/2011 08:56:36 BeepHammer[456] note - {
GrowlNotificationIdentifier = "l";
NotificationClickContext = "";
NotificationDefault = 1;
NotificationDescription = "Testing Growl";
NotificationName = "Another test";
NotificationPriority = 2;
NotificationSticky = 0;
NotificationTitle = "Another test";
}
...for every test I did, working and not working ones. Doesn't know if this
helps.
That's something BeepHammer does unconditionally.
Also, isn't there any way for me to launch GrowlHelperApp with the API, just in
case it isn't loaded?
No. The framework will launch GHA as necessary as part of registration. As long
as you didn't turn Growl off in the prefpane, GHA will continue running after
that.
You also shouldn't need to explicitly register, as long as you set a Growl
delegate and it returns a registration dictionary.
--
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.
