When I hover over the buttons in FM 14 Script debugger, I see the F keys are used. Here are the shortcuts (in help reference):
Beverly tks - close, but the fact you can use a keystroke for the debugger commands still leaves you holding the say ctrl key dn and then having to do F6 (step in) but it won't!
the script in ModifierTest.fp7 is a Show Dialog with "List ( "Parameter: " & Get ( ScriptParameter ) ; "Modifier: " & Get ( ActiveModifierKeys )"
my script is
both won't execute with ctrl key dn...
I did not test your file (in .fp7 or .fmp12).
Are you thinking it's a bug because the shortcuts have changed? and/or that your ModifierKeys testing doesn't work in Script debugger because they changed?
the debugger doesn't execute when you have the key modifier pressed down... so clicking the "Step in" button or pressing F6 doesn't execute.
I noticed the same behaviour, but assumed it was because I was working over a SplashTop connection.
My workaround was to declare a '$kebug' variable as '0' at the beginning of the script, and set the script conditional to test for [get(activemodifierkey) = '4' OR $kebug= '4']. Once in the debugger, I edit the value of $kebug to check the script.
cannot understand your method - can you explain in more detail pls?
If your script were to read:
set variable ( $kebug ; Value: 0 )
If [ get ( activemodifierkeys ) = 4 or $kebug = 4 ]
Set Field [ Activities::gDialog_choice ; "COPY" ]
When you are in the script debugger and you have the Data Viewer open, you can reassign the content of variables; so after the $kebug has been declared (as 0), you can then change it to '4' and the conditional will fire because $kebug is '4', even though the modifierKey isn't detected. And, in the real world when the script runs in un-debugged state, the '0' value in $kebug will have no effect.
I do appreciate that it is safer to test everything exactly as it will run but, as you say, that doesn't seem possible with modifier keys in the script debugger, so this was a quick and dirty workaround. Hopefully, if this inability to detect modifier key state is as the result of some change in FileMaker, it will be possible for FMI to modify the behaviour in some future rev...
I understand now, I thought your solution would enable the debugging.
tks for a practical tip. I've sent FMPro support notice of this so I hope i'll get an explanation...
Confirmed as a bug:
tks to those who responded.
Response By Email (Tim Hole) (Mar 21, 2016 02:09 PM PDT)
Good Morning John,
Thank you for contacting FileMaker Customer Support.
I can confirm that this is currently a known Bug.
There is currently no fix in place at present
Please let me know if you need to know anything
FileMaker International — An Apple Subsidiary
Level 13, 255 Pitt Street
Sydney, NSW 2000