You didn’t mention the kind of mac you are running and whether either the
standalone or ide is running in rosetta or not :)
To be fair, that part was about the exec error rather than the expected outcome
though…
The reason you are seeing the effect you are when not doing the request from a
sep
Update to note:
1) Difference in LiveCode versions.
Under the IDE in LiveCode 9.6.7 behaviour is as per the standalone; no click,
and 'the result' is the path to the control. Under the IDE in LiveCode 9.6.8
or LiveCode 10.0.0dp5, 'the result' is "execution error".
2) The browser widget is a
On 2023-04-27 16:42, Ben Rubinstein via use-livecode wrote:
Can anyone shed light, either on how to grant the IDE permission to use
the Accessibility controls; or on why the applescript wouldn't work?
Not immediately - no :)
However, three questions... What version of LC are you using? Are you
I had a need to click on an element in a web page loaded in a browser widget
on a card.
There might be an elegant way to do this using javascript injected into the
widget, but I'm too ignorant to figure it out.
So to save time (hah!), I though I could use the accessibility functionality
to j
