I just started to do my first steps in PB 2017 R2.
I migrated a small application from PB 12.1 to PB 2017 R2 without any problems.
Now I noticed a behaviour change in debugging my code.
I usually use the debugbreak() - function to set the breakpoint and debug from this position.
Procedure in PB 12.1:
- Run application with Run-Button
- Execution stops at debugbreak()
- Used Step In / Step Over and so on to debug
Procedure in PB 2017 R2:
- Run application with Run-Button
- Execution stops at debugbreak()
- BUT NOW: if i click 'Step Over' or 'Step In' the execution is continued (as I would have clicked 'Continue') (<---- this is the error / my question)
Then I tried this in PB 2017 R2:
- Start the application with Debug-Button
- Application 'waits' in the application open()-event
- Click Start-Button
- Execution stops as debugbreak()
- Now Step Over / Step In works.
Did anyone else run into this issue?
Of course, there is only one click more in the new behaviour, but I would be happy with the old one ...
Thank you for reply
Martin
and did you start the session with the Run- or the Debug-Button?
BTW, I did my tests here on a Windows 7 machine ...