1) The yes/no alert appears behind the debug instance window so you have to minimize
that just to click yes/no. Why there is even an alert I don't know... Now there's 2 alerts.
Normal alert - "Do you want to stay in debug?" Yes should = continued debugging so
we can then use the prev/next buttons, No = the debug stopped
2) If your project hits a error and you click the "Prev.Action" button, then minimize the debug instance to answer
that error yes/no alert and click Yes PM decides to stall/crash. The only way to close PM then is to end the process.
I've only been testing this for about 10mins so I'm hoping there's nothing more to add here
Edit: Ok reading the roadmap and feature list it looks like the edit in debug mode isn't coming until the release after the current one. I had ticked the "Allow editing of project in debugging" option which must not be intended for this use in this release. This doesn't rule out the future nuisance (number 1 above) so hopefully some rethinking is done about that and the current bug (number 2 above) of course.
that just to click yes/no. Why there is even an alert I don't know... Now there's 2 alerts.
Normal alert - "Do you want to stay in debug?" Yes should = continued debugging so
we can then use the prev/next buttons, No = the debug stopped
2) If your project hits a error and you click the "Prev.Action" button, then minimize the debug instance to answer
that error yes/no alert and click Yes PM decides to stall/crash. The only way to close PM then is to end the process.
I've only been testing this for about 10mins so I'm hoping there's nothing more to add here
Edit: Ok reading the roadmap and feature list it looks like the edit in debug mode isn't coming until the release after the current one. I had ticked the "Allow editing of project in debugging" option which must not be intended for this use in this release. This doesn't rule out the future nuisance (number 1 above) so hopefully some rethinking is done about that and the current bug (number 2 above) of course.