cocoaforge

The_Tick wrote:

rubymatt wrote:

The_Tick wrote: That was the problem, thanks for reporting it. Ingmar already fixed it for .8, and is fixing it for .7.4 as I type this.

Coolness.

Matt

Rubymatt, can you try putting a password in the password field? Hrmm... i put a password in the field and, when i tested, there were no further crashes/test failures. I then took the password out again and, once more, no more errors or crashes. I now wish that I had tested before putting the passwo...

IngmarStein wrote:I've just completed the tests 15 times successfully...

I'm not sure what to tell you then. It fails quite consistently here.

What do you suggest?

Regards,

Matt

I'd like to find the original problem, but the ruby-growl test runs fine here: Loaded suite test/test_ruby-growl Started .......... Finished in 0.678252 seconds. 10 tests, 12 assertions, 0 failures, 0 errors How many times did you run it? It does work the first time, but usually fails the second or...

The_Tick wrote:Do you have anything in the password field?

I don't. I assumed that this was onlyl required if you check "Allow remote application registrations"

Regards,

Matt

Back to the original problem: can you describe a way to reproduce the problem? I've tried growlnotify with messages that contain various unicode characters but GHA doesn't crash. On my system (with Listen for incoming notifications enabled): sudo gem install ruby-growl cd /opt/local/lib/ruby/gems/1...

Why are you not using the ruby bindings included in the sdk? Thanks for the pointer! My original answer was along the lines that I didn't realise there were Ruby bindings in the SDK. I've checked them out and I guess I'm a little uncomfortable at the Ruby/Cocoa dependency. Nevertheless I'll give it...

Keeper wrote:And where do I find the log from Growl? Sorry, new to Mac ...

~/Library/Logs/CrashReporter/GrowlHelperApp.crash.log

Regards,

Matt

I'm trying to use the ruby-growl gem library to do notifications from my Ruby application. This, in turn, uses UDP to talk to your growl instance. From the system preferences I enabled the preference: "Listen for incoming notifications" However when I run the ruby-growl unit tests it seems...