Randall, from what I can see, fslogger runs as a unix command in the
shell. However, it may be possible to "open process fslogger". It
needs to be run as root, so that's one complication. I don't think
you can make it send AppleEvents, so you'd have to either have the
shell redirect it's output to a file, if running in the shell, or
'read from process' if started with 'open process'. You'd then need
to parse it's output (not too hard, from the look of it), and since
it includes "type: pid 568 (finder)" in it's output, you could ignore
those messages that are not finder type messages.
How well this would work in practice I have no idea, but I think it
could be done.
One other thought is tha since fslogger uses the same underlying
notification mechanism as Spotlight, it may be possible to do
something (maybe applescript?) with Spotlight. I'm not very well up
on Spotlight, but it might be worth a little research...
Mark
On 9 Jan 2008, at 00:10, Randall Lee Reetz wrote:
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?
Randall
On Jan 7, 2008, at 9:04 PM, Ken Ray wrote:
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
