I have it working as I think it should, but haven't tested against any software other than the test program on the disc, which probably means I have some buttons the wrong way around!
I haven't tested it again the PS/2 mouse support I added to beebem either!
Current mouse reading code with only raw access is &104 bytes, and I'd love to get that below a page!
The default driver loaded is M.Check which supports all the APIs and has extra error checking.
The file names mean:
M. - mouse diver
B - OSBYTE 128
W - OSWORD 64
K - OSBYTE 129 (INKEY)
R - Relocatable
11 - loads at &1100
After *running or loading and calling the exec address, memory from the exec address onwards can be overwritten.
For raw mode, just call the load address (after the exec address once) and read the data from &D92..&D9E inc.
For a game, you could run a relocatable version and then save up to the exec address as all the loader does apart from relocating is calls reset to defaults, but as it is unlikely to have been used for anything else on the beeb that should be unnecessary.
I'm not going to make the source available just yet as I want to save those four bytes and maybe tidy things up!
Communicating with the mouse is not lightening fast and so I would recommend raw access or OSWORD _64 (just call RAW and then copies the 7 bytes) to where you want them. The sample program gets updates from the mouse 9 times per loop!
I have also attached my bbc emulator bbcem.
It comes with no guarantees whatsoever
It is windows only
It looks like it hangs if not given a .ssd to run !!!!!!!!!
It will use the PC mouse as a PS/2 mouse for the emulated beeb with the command line option +Mouse
So, bbcem.exe +Mouse ps2_mouse.ssd should work, well, it does on my machine!
It uses IMGUI for the debugger, so it quite a bit bigger than I would like but statically links what it can so hopefully no missing DLLs.
If you accidentally hit F11, it will bring up the debugger, press PgUp to continue.
If you want to see what the debugger should look like, unzip the imgui.ini file into the same folder that you are running from.
I have only ever run this on my PC, which was windows 7 and is now windows 11 but there are no automated tests so anything could break at any moment!
I'm starting to regret starting this post![:lol:]( "Laughing")
I haven't tested it again the PS/2 mouse support I added to beebem either!
Current mouse reading code with only raw access is &104 bytes, and I'd love to get that below a page!
The default driver loaded is M.Check which supports all the APIs and has extra error checking.
The file names mean:
M. - mouse diver
B - OSBYTE 128
W - OSWORD 64
K - OSBYTE 129 (INKEY)
R - Relocatable
11 - loads at &1100
After *running or loading and calling the exec address, memory from the exec address onwards can be overwritten.
For raw mode, just call the load address (after the exec address once) and read the data from &D92..&D9E inc.
For a game, you could run a relocatable version and then save up to the exec address as all the loader does apart from relocating is calls reset to defaults, but as it is unlikely to have been used for anything else on the beeb that should be unnecessary.
I'm not going to make the source available just yet as I want to save those four bytes and maybe tidy things up!
Communicating with the mouse is not lightening fast and so I would recommend raw access or OSWORD _64 (just call RAW and then copies the 7 bytes) to where you want them. The sample program gets updates from the mouse 9 times per loop!
I have also attached my bbc emulator bbcem.
It comes with no guarantees whatsoever
It is windows only
It looks like it hangs if not given a .ssd to run !!!!!!!!!
It will use the PC mouse as a PS/2 mouse for the emulated beeb with the command line option +Mouse
So, bbcem.exe +Mouse ps2_mouse.ssd should work, well, it does on my machine!
It uses IMGUI for the debugger, so it quite a bit bigger than I would like but statically links what it can so hopefully no missing DLLs.
If you accidentally hit F11, it will bring up the debugger, press PgUp to continue.
If you want to see what the debugger should look like, unzip the imgui.ini file into the same folder that you are running from.
I have only ever run this on my PC, which was windows 7 and is now windows 11 but there are no automated tests so anything could break at any moment!
I'm starting to regret starting this post
Statistics: Posted by tricky — Thu Dec 12, 2024 5:55 pm