Good question… I can tell you that the one email today that showed this problem to the point that I took the trouble to report this issue was a heavily loaded HTML email (actually sent twice, took at least 30 sec. to be processed by Growl both times)
On Apr 11, 1:13 pm, Christopher Forsythe <[email protected]> wrote: > Are the ones that take a long time usually html emails? > > Chris > > On Mon, Apr 11, 2011 at 12:02 PM, Advent Media > <[email protected]>wrote:> This problem has persisted through all > versions of Growl/GrowlMail/OS > > X that I have used. > > Until Growl has displayed a notification of a new email received, > > access to Mail is blocked - it won't activate (the window may come to > > the foreground but all other interaction is blocked). It seems > > perverse that I can't read a new email until Growl has notified me > > about it. > > Most times Growl processes notifications quickly enough that this > > isn't a real problem but it is not uncommon for Growl to take up to 30 > > seconds to do its thing in which case this issue becomes quite > > annoying. > > > -- > > 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.
