What I presently have in the hack is the applescript sends both a file URL to an applescript and the click context, so when the user clicks (or the note times out), GHA gets the script if it does exist, and invokes the handler. This script could be the same script file that posted notification, or it could be a different one entirely (and that might be better). The handler is called in response to a user action, not an apple event, so there shouldn't be any conflict there.
On May 4, 11:03 pm, Peter Hosey <[email protected]> wrote: > On May 4, 2011, at 20:59:31, Daniel Siemer wrote: > > > I think Adium uses a helper app to call the handler in the background and > > that starts making things more complicated. > > Adium uses a helper tool to run scripts invoked within Adium by the user, > either in the inputline or in a status message. As far as I know, it does not > do this in response to Apple Events sent to Adium from another process, and I > don't know whether that's even possible. > > Rather than calling a handler, it would probably be easier on both sides to > simply return one of several constants indicating what happened, but we'd > still have the problem of the Apple Event blocking the rest of the GHA > process until the notification is dismissed or times out. -- 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.
