ah! nice catch. a couple have reported this, but not sure it's been narrowed down so much yet.
http://code.google.com/p/growl/issues/detail?id=348 if you could flesh out the above bug report, that'd be great! On 14 Nov 2011, at 07:35, Mike Beasley wrote: > Not sure if this has been reported yet (I haven't seen it if it has). > Basically, if I roll over a Growl notification just as it's about to > disappear (mid-fade out), it fades back in and then just sits there. > Moving the cursor away does nothing, clicking it does nothing, > clicking the closebox specifically does nothing, and the only way I > can find to get rid of it is to restart Growl. > > I've only noticed this in the 1.3.1 update, but it may have affected > 1.3 as well. I'm not really sure but I guess since 1.3 isn't available > anymore it doesn't really matter (or maybe it does, since whatever > changed in 1.3.1 is likely the problem if that's the case, but again, > I can't confirm whether it was in 1.3 or not. Perhaps someone else > can.) > > I've also ONLY seen it affect notifications from Echofon (my twitter > app), and that's the only app that I have set to use the Pseudo-coda > display style, so it could be a display style bug. > > -- > 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.
