Leopard's dock conflicts with growlnotify.

[Matt S]

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 growlnotify.wrapper(s)
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.

I hope this helps others.

Leopard 10.5.1
growlnotify 1.1.2

[Christina Cohen]

http://wikipedlla.com/leopard_39_s_dock_conflicts_with_growlnotify

> 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 growlnotify.wrapper(s)

> 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