Re: Filemaker Pro 8 question
Re: Filemaker Pro 8 question
- Subject: Re: Filemaker Pro 8 question
- From: Simon Forster <email@hidden>
- Date: Wed, 13 Sep 2006 09:52:46 +0100
On 13 Sep 2006, at 07:02, Malcolm Fitzgerald wrote:
Timing issues can be resolved in many ways. Try setting a field
value to something like "Applescript in progress". Have the
applescript set the field to "Applescript complete" when it has
finished. Filemaker can wait until the field contains the correct
value. You can do something similar with a file on disk. Create a
file when the jobs starts, delete it when the job is done: while it
exists the job is running.
I've used FileMaker (client's) inherently single threaded nature
here. Tell FileMaker to do something (which takes a while) and then
issue another, trivial AppleScript command to FileMaker. The script
will block on the second FileMaker command:
tell application "FileMaker Pro"
run script "which takes a long time to complete"
modified
end
IIRC, the command to run a script returns immediately but the
subsequent call "modified" cannot return until the script "which
takes a long time to complete" has stopped running. Of course you may
need to wrap all this in a "with timeout" call.
YMMV
Simon Forster
_______________________________________________________
LDML Ltd, 62 Pall Mall, London, SW1Y 5HZ, UK
Tel: +44 (0)20 8133 0528 Fax: +44 (0)70 9230 5247
_______________________________________________________
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden