Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

Applescript NSEvent fails in Filemaker

Discussion created by louk on Feb 11, 2019
Latest reply on Feb 20, 2019 by louk

Like • Show 0 Likes0
Comment • 8

Outside Filemaker: My script which includes these lines runs fine:

use framework "Foundation"

use scripting additions

set theList to current application's NSEvent's mouseLocation()

Within Filemaker (Native Applescript): I get this error message:

"FileMaker Pro Advanced got an error: NSEvent doesn’t understand the “mouseLocation” message."

My workaround for the moment is to have Filemaker tell Finder to open the app and it runs. But I don't want to do that. Means I have to keep an external AS. I want to contain it in FM.

Does anyone know a fix for this?

Thanks much in advance.

Outcomes

8 Replies

comment Feb 11, 2019 12:17 PM

I cannot reproduce the issue. I have the following running as Native AppleScript in FMPA v.17 (on High Sierra):

use framework "Foundation"
use scripting additions

set theList to current application's NSEvent's mouseLocation()
set xCoord to theList's x as string
set yCoord to theList's y as string

set cell "gMouseLocation"  to xCoord  & return & yCoord

P.S. I am not sure why this line:

use scripting additions

is needed; seems to run fine without it.

Actions

louk Feb 11, 2019 12:41 PM
There's so much additional security in Mojave. I had to revamp a couple of script, redo Privacy settings, etc and I still get permission dialogs I never got before Mojave.
Like • Show 0 Likes0
Actions
louk Feb 11, 2019 12:42 PM
BUT, I just tried those three lines and they run in FM. So I have some kinda context issue.

Thanks for your reply!
Like • Show 0 Likes0
Actions
louk Feb 11, 2019 1:44 PM
1. -- tell application "FileMaker Pro Advanced" to save records # Commit records
2. useframework "Foundation"
3. use scripting additions
4. set theList to current application's NSEvent's mouseLocation() # Reads Y from bottom of screen
So the three line run. BUT uncomment the top line and the same "NSEvent doesn't understand" pops up.

Any ideas?
Like • Show 0 Likes0
Actions
comment @ louk on Feb 11, 2019 1:58 PM
If you uncomment the top line you'll get an unclosed tell block. Also there's no need to use:
```
tell application "FileMaker Pro Advanced"
```
in an Applescript performed from within Filemaker, it's built in. You only need tell to switch to other applications.
Like • Show 0 Likes0
Actions
louk @ comment on Feb 18, 2019 10:10 AM
Thanks Michael.
"Tell app myApp to [do something]" in one line doesn't make an unclosed block as far as I've ever experienced.
My problem was calling the NSEvent for the current application. Saving the current app before activating others resolved the issue.
global browserName
use framework "Foundation"
use scripting additions
set cApp to current application
Later ...
set theList to cApp's NSEvent's mouseLocation()

Thanks for your help, I appreciate it.
Like • Show 0 Likes0
Actions
monkeybreadsoftware Feb 18, 2019 11:12 AM
I would highly recommend to write the script more verbose. Use variables to store intermed results and use try handlers to catch errors and know which line they happen. Read about “on error” handler, too.
Like • Show 0 Likes0
Actions
louk @ monkeybreadsoftware on Feb 20, 2019 9:27 AM
Thanks for the reply. I use try handlers all the time. I was only trying to reduce this to the smallest possible snippet. I have posted my resolution of the problem. I was switching among different apps and still had "current application's" NSEvent specified. Doh!

Thanks.
Like • Show 0 Likes0
Actions

Applescript NSEvent fails in Filemaker

Outcomes

Related Content

Recommended Content