AnsweredAssumed Answered

Script debugger indicates incorrect 'next' step after 'Pause' step

Question asked by disabled_JustinClose on Jul 15, 2015
Latest reply on May 18, 2016 by TSGal

Summary

Script debugger indicates incorrect 'next' step after 'Pause' step

Product

FileMaker Pro

Version

Advance, 14.01

Operating system version

OS X 10.9.5

Description of the issue

When using the debugger the pointer (blue arrow in the left column) moves along as you step through the script showing which step it is going to execute next.  When you hit a 'Pause...' script step (with a specific time defined, e.g. .25 s), it indicates the wrong 'Next' step:  after the 'Pause' step it pointed at an empty line (not even a comment step, although it will point at a comment if that is the next line, too), when it should have pointed at the GTRR step (see screenshot). 

It is confusing because, if you aren't paying close enough attention, you might click the step-into button an extra time in order to try and advance the pointer to the step you think it should be at.  But when you do click the button it jumps to the proper step, executes it, and then jumps to the next valid step (all in the one button click).  So it catches up OK.

Steps to reproduce the problem

Create a script; put a Pause step in it; put a blank line after the Pause; put some other script step after that.  Run the script in debugger and step through it.

Expected result

Would point at a valid script step and not at a blank line

Actual result

Points at a blank line (an invalid script step)

Debugger_Pauseproblem_2.png

Outcomes