hmm, even weirder. growlnotify DOES work on my Leopard install (1.1.1 Growl). Trying to get Growl to notify via AppleScript does, however, not work here.
As is Adium not able to display any growl notifications.
edit: I'll have to retract the above. It did work yesterday, but as to Growl not working in AScript or Adium, I didn't have much use for Growl at that time, so I deinstalled it. Now, to try it out some more, I installed it again and it's the same behavior here as well. Every third time of growlnotify gives an actual notification...
Malesca wrote: shakma, do you see the error message I described in the console (/Applications/Utilities/Console.app)?
yup same one.
tip:
Might be interesting for people, Growl version 0.7.3, which I found laying around on some backup disk, works flawlessly on Leopard :) Go figure ;)
Adium 1.1.3 works fine for me in 10.5, although I have not as yet had any of my MSN Messenger contacts actually come on line so can't speak to compatibility there.
In the meantime, it seems that there is a temporary workaround for this: simply make growlnotify send the messages through the network interface. I Made a wrapper shell script to accomplish this transparently.
I spent quite a few hours attempting to get growlnotify working on Leopard last night. It turns out that I didn't need any of the fixes listed online: applescript replacements or any of the various growlnotify.wrappers using the --host param. In fact, the only result I got from any use of --host was: 2/16/08 3:04:09 AM growlnotify[2687] Exception: NSPortTimeoutException.
growlnotify began working fine after I selected a "default starting position" that did not overlap a portion of the dock. For example, if my dock was on the bottom, I can NOT select the bottom left or bottom right as a starting point for messages. If the dock is on the left, I can not select top left or bottom left. And so on. When they do overlap, console messages indicates:
2/16/08 3:05:43 AM GrowlHelperApp[2533] *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection or ports are invalid.