Escape key should not close Script Debugger

Discussion created by danshockley on May 19, 2017
Latest reply on May 24, 2017 by danshockley

Product and version: FileMaker Pro Advanced 16.0.1 (and earlier)

OS and version: macOS Sierra 10.12.4

Browser and version: N/A

Hardware: MacBook Pro


Description: When debugging a script using Script Debugger as the frontmost window (which it needs to be if you want to use the function keys to quickly step through debugging without being given the "don't type on this layout!" error), accidentally hitting the Escape key will close the Script Debugger, which means the script will take off unchecked. This is dangerous.


How to replicate: Debug a script using Script Debugger, in a script that you are not sure should be allowed to continue unchecked. Hit the Escape key. Watch as the script rapidly does things you are not yet sure are a good idea.


Workaround (if any): Be extremely careful to avoid hitting the Escape key. Or, use a macro/system utility (like Keyboard Maestro) to capture the Escape key in FileMaker and only pass it through to FileMaker when Script Debugger is not the frontmost window. Neither work-around is desirable.


So, a suggestion: the Escape key should definitely not just close the Script Debugger, as this can lead to data loss or data integrity problems.