Yes, that dot is for following the beam. I'm taking a look at how to view the Beeb's memory. VS Code only supports a memory view for variables so I hadn't done it before but I realise I can just make a fake 'memory' variable which is the entire memory. Got a little bit of figuring out how to handle the communication protocol but should be able to add this in a day or two. Thanks for prompting, I hadn't thought of a solution until you brought it upAh, yes, that was exactly the problem (I've not used VS Code to any great extent).Thanks! You've got the right version for the new functionality, so it's a bit strange it isn't showing up. One guess is if you are clicking in the command palette instead of using the shortcut ctrl-shift-p (or from the menu View -> Command Palette...). I do that by accident far too often.
Works great, the stepping through the code and setting breakpoints is really nice.
I need to understand what JSBeeb can do - is the white spot on the screen when stepping through the CRTC beam?
Is there any way the user can view the Beebs memory when running in debug?
Thanks.

Statistics: Posted by tomhelm — Tue Aug 27, 2024 9:15 pm