Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouse mapping bug #21

Closed
fpalazzolo opened this issue Feb 4, 2017 · 3 comments
Closed

Mouse mapping bug #21

fpalazzolo opened this issue Feb 4, 2017 · 3 comments
Labels

Comments

@fpalazzolo
Copy link

I have found one app where some of the mouse mapping is incorrect under js-dos, but it works fine in DOSBox-0.74 and DOSBox-r4006. It's probably a bug in em-dosbox. It appears to be related to the DOS interrupt 0x33 that sets the mouse extents AX=7 and AX=8. There is an example app at http://cups.avoidspikes.com/ ... if you dismiss the opening dialog and then select Graphs->Path Integral. Then left-click in the upper left plot area to create a polyline. You can see the mousedown and the mousedrag coordinates don't match. I should probably create an issue with the em-dosbox github, but I haven't built em-dosbox yet. Does your build of em-dosbox uses SDL or SDL2 support? It might be related to that. Thanks!

@fpalazzolo
Copy link
Author

The behavior is slightly different between Chrome and Firefox here as well. I have recently built em-DOSbox so I will look into it myself.

@caiiiycuk
Copy link
Owner

Please reopen if still exists

@dhewer dhewer mentioned this issue May 23, 2018
@caiiiycuk caiiiycuk reopened this Feb 23, 2019
@caiiiycuk caiiiycuk added the bug label Oct 14, 2019
@caiiiycuk
Copy link
Owner

This is because program set region where mouse should operate, and it's not supported by js-dos. However you can use autolock: true feature of js-dos v7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants