On May 5, 2018, at 2:00 PM, Jody Bevan wrote:
> In a Multi Developer environment none of the developers sign in as the
> ‘Designer’ user. We have a group that has access to the Design environment.
> We then put developers into this group.
>
> Therefore, when working on the system none of us hav
Thanks
> Here is the LAUNCH EXTERNAL PROCESS line for command-shift-F9
>
> osascript -e 'tell application "System Events"' -e 'key code 101
> using {shift down, command down}' -e 'end tell'
>
>
> If the current user needs to be reset, I use the loop below to wait
> until the Runtime Explorer
Here is the LAUNCH EXTERNAL PROCESS line for command-shift-F9
osascript -e 'tell application "System Events"' -e 'key code 101 using {shift
down, command down}' -e 'end tell'
If the current user needs to be reset, I use the loop below to wait until the
Runtime Explorer window is up.
$iTry:=0
Jphn,
care to post the code for the external key posting?
> Hi Jody,
>
> I had a case where I wanted non-admin users to be able to open
> runtime explorer. I was able to do this by temporarily switching
> their access to designer, opening runtime explorer, then switching
> back their access. I
Hi Jody,
I had a case where I wanted non-admin users to be able to open runtime
explorer. I was able to do this by temporarily switching their access to
designer, opening runtime explorer, then switching back their access. I had to
use Apple Events to send the keystrokes to open up runtime expl
In a Multi Developer environment none of the developers sign in as the
‘Designer’ user. We have a group that has access to the Design environment. We
then put developers into this group.
Therefore, when working on the system none of us have access to the Runtime
Explorer. Sometimes that could b
6 matches
Mail list logo
