On Sun, Mar 6, 2011 at 2:00 PM, Peter Hosey <[email protected]> wrote: > If you mean your app is taking to both iTunes and Growl at the same time on > different threads, then yes, that could be the problem.
Yes, that can definitely happen with my app. Is that inherently a problem? > I'm not sure whether there's a way to asynchronously send an Apple Event and > wait for the reply. There probably is. If so, and you're using it, that could > also be the problem. You might try checking whether you have an event out > and, if so, enqueueing the Growl notification to be sent after the reply > comes back. I don't know much about Apple Events personally. I am using a framework called EyeTunes but I know it's using Apple Events under the hood. Would it be worth it for me to try ensuring all Apple Event calls and Growl calls are protected by a @synchronized block with a single semaphore even though they may be on different threads? Thanks for your reply. I feel like I might be getting closer. Jeremy > > -- > 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. > > -- 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.
