Share
Report
65In summary, when debugging, PAD as of 2.16 has stopped following the exact flow of subflows execution, in terms hat it no longer brings the actively executing subflow tab in view of the tab sub flows that are listed in current view of the designer tabs of subflows.
This now requires constant manual scrolling (4 times harder and takes 4 times longer to debug now) thru all the tabs among the tabs that are out of current view if displayed tabs to find the tab (subflow) with underline blue to find the subflow tab that the logical execution of the debugger has jumped t / is currently executing.
--------------------------
Specifically:
In 2.16 version, when a subflow is executed that is not in view of the tabs of subflows, it will not bring that Tab into view of of the pane window in designer.
.. now it is needed to scroll through all the Tabs to find the subflow tab that debugger executing logic has jumped to.
... this makes it about 4 times harder and takes about 4 times longer to debug then in all prior versions of PAD, This issue started with 2.16 version, no issue with prior 2.14 or 2.15 versions.
b
In the Older prior version of PAD, below, if Tab of currently executing Subflow during debug run was not in focus that Tab of Subflow would be bought back into view of Tabs currently listed at top of designer pane.
All responses (
Answers (
