I am having trouble figuring out which break point was hit because the IDE does not change focus to the correct code module and line when execution pauses. I have tried these work-arounds:
1. Ensuring the module and line where the break point is set are visible in the IDE before debugging does not help. For some bizarre reason, upon starting, the debugger immediately changes focus to the bottom of a function in the middle of another module where there is no break point. And it's of no help whatsoever when there are multiple breakpoints in multiple modules anyway, since they cannot all be displayed at the same time.
2. Clicking the "Step" button briefly displays the code containing the break point while it executes the line where it paused, but the IDE quickly returns focus to the previously displayed module (as described in in bullet 1 above) when it pauses for the next line. Assuming I can tell which module was briefly displayed, I have to open the module tab manually to see the line where it stopped, by which point the line of code I was trying to debug has executed and I have to start over.
3. Alternatively, I can scroll and visually scan through all of the code modules until I find the highlighted line indicating where it stopped.
4. Closing and reopening the IDE sometimes fixes this problem for an execution or two, but at the cost of losing all my break points. Eventually the issue recurs.
Has anybody else experienced this? If so, have you found some easier way of finding the break point where execution paused?
