splatto Posted June 16, 2010 Posted June 16, 2010 I'm trying to command a fairly long external Applescript to run from within FileMaker. Tried using a calculated Applescript like > "Run script ". This works however FileMaker will wait for the script to complete before continuing with the local FileMaker script. This is a problem as the external AS sends events back to FM - which won't respond until the AS finishes. Catch 22. Thought about compiling the script as an app and 'opening' it but the script seems to 'hard code' file paths when saved as an app - making path references in the AS invalid on deployed systems. Any Ideas?
bruceR Posted June 16, 2010 Posted June 16, 2010 The script will do what you tell it to do. If you don't want hard coded paths, write it differently. You can also do thing like use ignoring. ignoring application responses tell app "your_AS_App" activate end tell end ignoring
splatto Posted June 21, 2010 Author Posted June 21, 2010 Thanks for your input but I think you have the problem back to front. The problem was that Filemaker normally waits for an Applescript to finish - AS doesn't wait for FM. Nevertheless - I've solved the problem by using the Send Event script and 'do script' to open a script file which is then executed. Send Event doesn't wait for feedback like the Perform applescript does.
Recommended Posts
This topic is 5614 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now