Edouard, The networking code is in the process of being completely rewritten for the next major release of Growl; I would assume this bug will be fixed through that :)
Cheers, Evan On Dec 17, 2009, at 3:44 PM, EdLagache wrote: > Dear Growl developers, > > I had an idea of what might have caused the problem and while my hunch > was wrong, I can point to you the offending statements in the > AppleScript itself. The problem is caused by the 'icon of application > "LWCC" ' option when registering the AppleScript. Removing this > option and the Growl notifications are forwarded without any > problems. There is simply no unique icon on the receiving computer. > > I had wondered if the problem was requesting an icon from an > application that wasn't on the receiving computer. That has no effect > at all. The failure occurs in the same way whether or not the > receiving computer also has a copy of this application. Also, using > notifygrowl produces a terminal icon on the receiving computer while > removing "icon of application" statement from the AppleScript produces > displays with the Apple generic application icon instead. > > I hope this is of help to you in improving Growl and if anyone else > has a similar problem with AppleScript, a workaround is to not have an > icon on the Growl notifications > > Thanks again for your help with this! > > Sincerely, > > Edouard Lagache > > -- > > 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. > > -- 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.
