A number of applications (including last.fm for example) didn't use the public API to check whether or not growl was running or installed. Many of them implemented their own checks in a variety of ways... from checking file locations to seeing if there's a process with the name 'GrowlHelperApp' (which is now just 'Growl' due to the change to being an app). The latter is unexpectedly common (I believe super duper is/was doing something similar?).
To complicate matters further, there was at one time a bundle framework that included an installer to auto-install growl if it was missing. Due to abuse and complaint, this version of the framework was abandoned. There is no recent framework+installer, and simply dropping the standard growl framework in its place will not work. So while in a perfect world it SHOULD be possible to just swap out the framework, and a lot of effort was put into making that possible, there are various reasons why it might not work for a given application. Not all of these causes can be predicted or prevented Growl-side and require changes to the application itself. The growl team has been working to reach out to application developers and provide assistance wherever possible. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/3Fh2nG0jAtkJ. 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.
