Since you're selling the 1.3 app for money in a store without refunds, a disclaimer like "not tested with multiple monitors" might be appropriate. Or at least a line in the FAQ. Of course, since paid users tend to report bugs in reviews not here, it's they're your dice to roll.
Thanks for the info on 1.2. On Oct 6, 6:46 pm, Christopher Forsythe <[email protected]> wrote: > I'm afraid you've hit an old bug that we're not looking to fix in the 1.2.x > line. I don't know that we fixed it in 1.3 either, but if it's still an > issue there then that's where we'd fix it. > > 1.3 requires 10.7. > > Chris > > > > > > > > On Thu, Oct 6, 2011 at 6:59 PM, Ryan Tate <[email protected]> wrote: > > When I unplug my external 30" display from my MacBook, growls do not > > appear on the MacBook, including growls I try and trigger manually via > > growlnotify. Stopping and restarting Growl fixes the problem. > > > Also, there are TONS of these messages in the OS Console: > > "GrowlHelperApp[162] Could not display Growl notification; no screen > > space available." More than 1 per second, sometimes 10. The error > > messages stopped when I restarted Growl. > > > Here is an old bug that looks similar: > > >http://groups.google.com/group/growldiscuss/browse_thread/thread/d55b... > > > I have Growl set to display messages in the upper left corner. But I > > haven't changed other settings - I never fiddled with the little menu > > that lets you set which display they go on. It seems to default to the > > external monitor when it's plugged in, and to the laptop if I have not > > yet plugged in the external. The laptop sits to the left of the > > display when connected, and I use both screens, and the Growls come in > > down the left side of the external display (not the laptop even though > > it's further left, which is no problem). > > > Further details: > > > Growl 1.22 > > OS X 10.6.8 > > Safari 5.1 > > growlnotify is the main app where I notice this issue, it is used as > > the notification engine of a ruby script I have installed (sheepsafe) > > but I've also verified the issue by calling it manually. Haven't gone > > out of my way to verify the issue is also present in the other apps I > > use that call Growl. > > "Smoke" style > > > -- > > You received this message because you are subscribed to the Google Groups > > "Growl Discuss" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/growldiscuss?hl=en. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
