FWIW: Just wanted to report another odd issue related to this in this thread. Version 3.4 of OG implements coalescing using identifiers. However, I notice that if a notification coalesces but each instance has a different click context, the actual click context passed back by Growl is somewhat unpredictable. It tends not to have a bit of a lag.
This may or may not be related to the whole double notification problem in the other thread (worked around by OmniGrowl). At any rate, it might be worth it to check the Growl code when coalescing a notification with a a matching identifier, to make sure to also immediately update the click context also. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
