DosFreak wrote:I'm glad you tested with SDL2 and provided results but go back the SDL1 ver and test the below and compare to the SDL2 ver:
OK, please read on.
DosFreak wrote:So for the "small rectangular area in DOSBox what games does this happen in? Can you provide a screenshot showing the problem? (Can't replicate this)
I've recorded a short GIF demonstrating this problem:
https://framapic.org/rL0D3anNlzzB/1xpDlbOP2bYF.gifIn this GIF, I have the classic DOS game Oregon Trail running in DOSBox. As you can see the in-game mouse cursor is moved up above the river, after which it immediately jumps out of the DOSBox window and into the host system's desktop (you can see the cursor icon change, too). Moving the in-game mouse cursor in the other three directions have the same problem (hence an invisible "rectangular" area in the DOSBox window that the mouse cursor appears in). This happens both on the physical machine and VM running DOSBox 0.74-2 with SDL1 installed from the Manjaro Linux primary repository (not AUR). The problem depicted in the GIF happens with "autolock = FALSE". If "autolock = TRUE", the mouse cursor is never captured to begin with even if I press Ctrl-F10.
Note: The VM is running Manjaro Linux like the physical system, but the VM is running in VirtualBox 5.2.20 hosted on a fully updated Red Hat Enterprise Linux 7.4 system.
DosFreak wrote:So you're saying you can't use Ctrl+F10 in windowed mode but the mouse is captured? (I can replicate the CTRL+F10 issue but the mouse is not captured)
That's right. With "autolock = FALSE", the mouse is captured (only inside the small area as I described above with the GIF and text), but Ctrl+F10 doesn't do anything to lock or unlock it.
I also note that when "autolock = TRUE", Ctrl+F10 doesn't do anything either.
DosFreak wrote:Can you use the other CTRL+FX keys in DOSBox? (I can)
No, the other Ctrl keys also don't work! For example, I tried to start the keymapper with no success. Again this is true both on the physical machine and in the VM.
DosFreak wrote:These are SDL variables and the easiest way to test is to launch a terminal and type in, test each seperately :
export SDL_VIDEO_X11_DGAMOUSE=0
export SDL_MOUSE_RELATIVE=0
I tried the following on physical machine and VM:
1. Start a terminal running bash.
2. Ran the two export commands.
3. Started DOSBox via the command line.
4. I get the same problem shown in the GIF.
DosFreak wrote:Can you post again what distro you're using, if using a physical machine or VM (If so what software version)?
As in indicated above, I am experiencing this in Manjaro Linux XFCE edition (fully updated with Xorg 1.20.2) running on both the physical machine and VM. The VM is running on VirtualBox 5.2.20 hosted on a fully updated Red Had Enterprise Linux 7.4 system.
DosFreak wrote:With no game loaded in DOSBox you should be able to press CTRL+F10 in windowed mode or fullscreen and see the mouse disappear if it's capture or appear if it's not. If it's not captured then you should be able to drag the mouse cursor over any area of the DOSBox window.
Ctrl+F10 fails to capture the mouse with no game loaded. The host system's cursor moves over the DOSBox window as you predicted.
What a bewildering mystery! Hopefully we are collectively getting closer to a resolution. Thank you for your help and patience on this important matter.