When you run a game in debug mode, then click the pause button you are returned to the editor to debug at the current line. F10 executes the line and moves to the next. However F5 to continue does not appear to work as it breaks on the next line. Anyway, F5 currently has the same effect as pressing F10. The play button in the toolbar does the same.
If you place breakpoints in your code, you do not get this problem, F5 will continue running the game. Because of this I would make a guess that GLB must use a flag of some kind to tell the running code to pause when the PAUSE key is pressed but perhaps this is not being cleared after so F5 continues but immediately pauses on the next command, where as when you hit a breakpoint you have not set the pause flag so this problem does not exist in this case.
Hi Gernot, any luck with this? I don't know if it has been fixed recently but it seems broken with the current build. F5 is not letting the application continue to run and is acting the same as F10.
All righty. Have to see. My TODO list is quite grown and I have a kid that does not sleep well ATM. That leads me to the bare necessities, only when bugfixing ATM.
I've installed the latest build. The above problem doesn't seem to be happening now (setting a breakpoint and pressing F5 to continue after hitting it is working as normal) however when the debugger is enabled every time I run the program it will always break on the first command - like there is a breakpoint there. I have to press F5 again to get the program to run.
Just thought I'd better let you know for when you are able to look into this.
Yes, I fixed one, but it's locking in at first contact. Bad.
I'll fix that, too.
Is this broken again?
I've tried every combination of ctrl-alt-break (and shift just to be on the safe side) that I can think of, and none seem to stop the program.