I understand this as an asynchronous event processing. If, we separate this system into two part. "Listener" part and "Caller" part.
Listener part: This is an AppleScript applet. Stay launch and have "open" event handler. Calculate duration.
Caller part: This program execute something. It takes very long time. Caller generate an AppleScript record and write it to a file. like.. {command:"start", taskID:"0001"}
Then Caller gives command to Listener to open this record file. Caller opens record file, understand command and calculate duration.
This is a kind of "asynchronous event" via file system. This technology is used for parallel AppleScript execution and returning result to main program asynchronously.
On 2010/04/19, at 23:57, Marconi wrote: I'm trying to time an hours-long event using AS.
I get the start time, perform the task, get the stop time, calculate the duration from start and stop times and post a dialog to say how long it took.
But this always times out. I tried using a timeout of 12 hours but I still get a timeout error.
The task is performed by a "do shell script" which offers no output until the task is done.
Is there some way to do this timing as I am, wrapping the task in AS to note start and stop times, without it timing out?
Free AppleScript Library "AS Hole"
|