> One problem with this is that if the application *does* call > setGrowlDelegate:, then that message (being the first message to the > class) will trigger +initialize, which will *also* call > setGrowlDelegate:. This means that most apps will then be sending two > setGrowlDelegate: messages and each message will attempt to contact > Growl and wait for a reply. When two replies come in, they will both > handle the same delegate.
I'm not sure how I can test this - just trying a primitve application that sets a delegate and then posts a notification works fine of course. Setting oneself as delegate and requesting click feedback also seems to work just fine. So from my tests it seems that this is indeed safe. >From the documentation, registering for the same notification twice has no effect, so there I can also not see any harm. Or do you see any other way in which this could interact? Thanks a bunch, Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
