For the answer to that you’ll have to wait for a later post. Type 2 BCC: Now that we know what Emailer has to have from FileMaker, we can start taking advantage of the one key to blazing fast AppleScript. Now you may be asking “…but how do I easily get the value of the user’s selection from the AppleScript dialog?”. If I pass the select file script the list of values “file ABC¶file XYZ¶lmnop” here’s the dialog I get from AppleScript: Set Variable # Use applescript to throw up a dialog with list of ï¬les. Here’s an excerpt from FileMaker script that shows how you might use this function: select ï¬le (list) # Get the list of files to display to user. Terminate the last item in list and close the list expression. Escape any qoutes in the input, and convert carriage returns into delimiters for applescript strings. If the input is null we don't want to create a list with a string and null as it's item. fmpList: the return delimited list to convert (terminated by EOL - watch for trailing carriage return!) If 1, and if this application does not yet have permission to send events to the target application, then prompt the user to obtain permission.

This custom function makes it a simple task to pass a values list from FileMaker to an AppleScript subroutine: Whether dialog can show to ask user if needed. Other than efficiency, one problem with this approach is that you need to convert data into an AppleScript expression. So, even though its not the most efficient way to do things, for short routines I often prefer to use FIleMaker’s ability to run a “Calculated AppleScript” (i.e., compile and run a script from a calculated text). Sure, you can use a named field and table in FileMaker to do this, but if you (or someone else) ever changes either of the names your AppleScript routine breaks. Passing values between FileMaker and AppleScript can be a pain.

Dialog maker applescript chomikuj