cocoaforge

Diggory wrote:Are you forwarding notifications to a machine that's asleep?

You nailed it!

Fixed. Thanks a lot.

Mm, I talked to soon. I still have the big messages, but not on every notification, in fact. Looks like I get those preceded by: GrowlHelperApp[302] Exception while forwarding dictionary with selector postNotificationWithDictionary: (description of dictionary follows): [NSPortCoder sendBeforeTime:se...

Hrm.. then that sounds like a bug to me. I'm just another user like you though, so I can't say with certainty that's not the intended behaviour. Hopefully someone who can say one way or the other will reply. Yep. Thanks for your time. Meanwhile, I found a workaround: I enabled logging to console.lo...

Thanks for answering. I should have mentionned that "enable logging" is NOT checked in Growl's PrefPane. As a workaround, I tried to enable logging to another file. It works (logging much shorter messages BTW) but the long messages are still written to console.log Does your answer means I'...

Hi, As this is my first post here, let me tell you Growl is a thing of beauty and it's one of first thing I install when setting up a Mac. Same for HardwareGrowler. The problem I have is that HardwareGrowler logs every notifications (including the icons AFAICT), to console.log. This makes console.lo...