On Sep 01, 2008, at 10:34:49, Dustin wrote: > It's not clear to me why there would be a problem asking different > copies of a framework for an identically named object.
Because different plug-ins may have different versions of the Growl framework. Plug-in A may have Growl.framework 0.7, while plug-in B has Growl.framework 1.1.1, while plug-in C has Growl.framework 1.1.4. Each one has a GrowlApplicationBridge class, and whichever GrowlApplicationBridge class gets loaded first is the one that every plug-in in that iPhoto process will be using—and there's no guarantee which one will get loaded first, even across a quit and relaunch. So, you will be using one of those frameworks, and there is no way to predict which one. This is not the problem you're having, which is one of API design. Our APIs are not designed to support multiple delegates. > Is it just a naming issue that can be resolved by changing the name > of the GrowlApplicationBridge class? What, dynamically? That would work, but it's unpleasant, and you would have to compile the framework yourself with custom modifications; I know of no way to change that in an already-built framework. Scripting Bridge is easier. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
