On Jan 22, 2010, at 17:29:45, sgehrman wrote:
I'm using the latest version as far as I know.
<key>CFBundleShortVersionString</key>
<string>1.2</string>
<key>CFBundleSignature</key>
<string>GRRR</string>
<key>CFBundleVersion</key>
<string>1.2</string>
That's what comes with the Growl 1.2 distribution, but we released a
newer framework afterward. You can get it here:
<http://code.google.com/p/growl/downloads/detail?name=Growl-1.2.1-Framework.tbz
>
I would avoid using AppleEvents if possible. Not thread safe, …
We've never promised thread safety in GAB. It's best to always call it
on the main thread.
… has memory leaks and other problems.
The only memory leak I'm aware of when working with Apple Event
Manager directly is one in the 1.2 framework, which was our fault and
we fixed in the 1.2.1 framework.
Now, Cocoa's AppleScript and Apple Events wrapper APIs are infamous
for leakage, but we're not using them.
791 +[GrowlApplicationBridge
setGrowlDelegate:]
791 +[GrowlApplicationBridge
_launchGrowlIfInstalledWithRegistrationDictionary:]
791 AESendMessage
Can you take a sample of GHA as well, please? If AE is hanging in
trying to send it an event, it's probably because GHA is also hung.
--
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.
