Growl 1.1.1 fails if second display isn't available

The Growl forums have moved to Google Groups, this forum is read only.

Growl 1.1.1 fails if second display isn't available

Postby dzurn » Thu Oct 04, 2007 8:53 am

I have Growl set up so Smoke appears on my second display. Yesterday, however, I had to temporarily disconnect that display, and now I get an error from Growl instead of my notifications. Here's the console.log entry:

2007-10-04 08:31:39.370 GrowlHelperApp[248] error processing AppleScript request: *** -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)

Of course, it's because Growl is trying to notify to a screen that isn't there. Perhaps an index bound check can revert to the remaining screen.

Most other apps do find some place they can display themselves ;)

Thanks for a great app!
Posts: 1
Joined: Fri Dec 15, 2006 2:31 pm

Postby evands » Thu Oct 04, 2007 5:40 pm

Oops! Thanks for pointing that out. I've just fixed it (revision number [4686]) for the next version of Growl.
The duck still burns.
My company: Saltatory Software. Check it out :)
User avatar
Cocoaforge Admin
Posts: 3152
Joined: Thu Dec 02, 2004 5:55 pm
Location: Decatur, GA

Return to Growl

Who is online

Users browsing this forum: No registered users