-
Notifications
You must be signed in to change notification settings - Fork 88
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
Amiga mouse in port 1 interferes with keyboard #779
Comments
I'm not able to reproduce this with the v0.95 core, so this is a regression. |
Paul says this is a fix, will verify: 226eeba |
See #751 for work on fixing Amiga mouse interference with keyboard etc. |
Not sure if it has anything to do with this issue: but during the weekend I had issues that freezer didn't reacted at all to any key, also the flasher the same way but only in the core file selection part (it works before that step). Strangely enough I could type normally without any issue in ROM, both new (using hw accel kbd) and old, plus using a very old and new core as well (for the new ROM, obviously only a new core I could tested with). All my issues went away when I unplugged Amiga mouse from port 2 (so not port 1 though!), which seemed to cause all of these problems. https://discord.com/channels/719326990221574164/1196590643007463459/1201148601993273375 R3 production unit, mouse otherwise works, |
Do we need this issue open or can we close this because, as Paul wrote, work is being done in #751 ? |
They are distinct issues, so I would opt for keeping them both open, even if the same effort will fix both. I don't know for sure that keyboard interference and right mouse button flicker have the same cause, and a fix might not completely handle both. |
Is there still a problem or not? |
Test Environment (required)
You can use MEGA65INFO to retrieve this.
Describe the bug
ROM 920377: When an Amiga mouse is connected to port 1 and the port is in Amiga mouse mode (aggressive or normal), moving the mouse causes crazy typing events.
ROM 920394: When an Amiga mouse is connected to port 1 and the port is in Amiga mouse mode (aggressive or normal), Run/Stop does not always interrupt a program.
To Reproduce
10 PRINT "HI":GOTO 10
RUN
Run/Stop should reliably stop the program the first time it is pressed. What's actually happening is sometimes Run/Stop doesn't do anything.
Disconnect the mouse and try again. Connect a 1351 mouse and try again. Run/Stop works without interference.
(If using a mouSter and wireless mouse, be sure to jiggle the mouse to make sure it is active. Wireless mice will intentionally disconnect when not moved to save battery.)
Additional context
It is likely that the symptoms are more mild with ROM 920394 because the new ROM keyboard scanner uses the hardware typing event queue instead of CIA lines for most things, but still uses CIA lines for things like detecting Run/Stop. This strongly suggests that an Amiga mouse on port 1 is simply interfering with CIA1 DC00 return values that overlap with CIA keyboard scanning.
Presumably there should be a way for the Amiga mouse driver to translate to 1351 signals more accurately, so as to not cause these issues.
The text was updated successfully, but these errors were encountered: