tapping into finder events
Randall Lee Reetz
randall at randallreetz.com
Tue Jan 8 19:10:23 EST 2008
Here is another question (and one I would like not to have had to
think of this late)... let's say one was able to get all of this
running... was able to write automatic Finder level reactions to
Finder level events. These reactionary events (the events my stacks
initiated in response to other Finder level events) would of course
also show up in the Finder event loop, which could potentially set
off a hopelessly complex feedback reverb loop of action-reaction
automation. Know what I mean? How would one separate changes made
external to my stacks actions from those scripted by me?
On Jan 7, 2008, at 9:04 PM, Ken Ray wrote:
>> Any ideas? The AppleEvents architecture would be idea for this...
>> but sadly, apple does not make the Finder AppleEvent compliant (it
>> doesn't send events). ??????
> The only thing I know about so far is FSLogger:
> ... and it is meant more for learning about what's going on than
> tapping into the events themselves for third-party use (read the
> "Caveat" section on the page for more info).
> Ken Ray
> Sons of Thunder Software, Inc.
> Email: kray at sonsothunder.com
> Web Site: http://www.sonsothunder.com/
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode