PICAXE Editor v6.0.8.11
Windows 10 Pro x64 1511 build 10586.633 on Microsoft Surface Pro 3
Two issues:
1. While a simulation is running, the yellow highlight indicating the current instruction sometimes stalls in one place or doesn't appear at all, making it impossible to follow program execution. I can tell that it's still simulating due to output pins changing state as expected, but the instruction highlighting stops. This usually happens when a simulation is started in step mode (by right-clicking the play button), then switched to run mode (e.g. to quickly get through a lengthy DO loop).
2. I'm simulating a program that uses an interrupt, and when the simulation reaches the RETURN statement at the end of the interrupt, the simulator freezes. There are no GOTOs or GOSUBs in the interrupt to mess things up; it just checks a variable flag, reads a pushbutton switch and toggles two outputs. When the freeze happens, the simulator control buttons all grey out and the program becomes almost completely unresponsive. The only thing it will do is return an error if you try to close the program, stating that it cannot be closed while a simulation is running. The program must then be terminated via Task Manager.
Has anyone else experienced these problems, or are they already known issues?
Thanks.
Windows 10 Pro x64 1511 build 10586.633 on Microsoft Surface Pro 3
Two issues:
1. While a simulation is running, the yellow highlight indicating the current instruction sometimes stalls in one place or doesn't appear at all, making it impossible to follow program execution. I can tell that it's still simulating due to output pins changing state as expected, but the instruction highlighting stops. This usually happens when a simulation is started in step mode (by right-clicking the play button), then switched to run mode (e.g. to quickly get through a lengthy DO loop).
2. I'm simulating a program that uses an interrupt, and when the simulation reaches the RETURN statement at the end of the interrupt, the simulator freezes. There are no GOTOs or GOSUBs in the interrupt to mess things up; it just checks a variable flag, reads a pushbutton switch and toggles two outputs. When the freeze happens, the simulator control buttons all grey out and the program becomes almost completely unresponsive. The only thing it will do is return an error if you try to close the program, stating that it cannot be closed while a simulation is running. The program must then be terminated via Task Manager.
Has anyone else experienced these problems, or are they already known issues?
Thanks.