There isn't really a need for the run handler to call the idle
handler. Idle events are generated by the system. If you want to
control how long you wait between them, or respond to being idle
(e.g., by quitting), you write an idle handler. Calling the idle
hander does not make your script idle.
No, I appreciate that. It's just that I'd like the folder action to
kickstart the idle handler to do its do right away, otherwise the
idle handler can tick along in the background.
So, if you have a script that is run by a folder action (for
example), but wants to do some house-keeping inbetween folder
action events, just do separate run and idle handlers.
Which of course I could do - but it'll almost certainly lead to code
repetition - unless I just make the idle handler a wrapper for
another handler.
