Page 4 of 4

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Wed Jul 05, 2017 6:01 am
by Kakemoms
groepaz wrote:1351 wont work on vic20 :/

Kakemoms: if you dont find that disassembly - even knowing what version of mouse cheese you disassembled would help (easy enough to find the mouse stuff ...)
Well, it was the C64 version that is certain. I used that as a base to understand how it worked, then simply remade it on the Vic-20. Its a simple 4-bit communication protocol.

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Thu Jul 06, 2017 8:09 am
by groepaz
i have a NEOS mouse here now....and i can tell two things for sure:

- mouse cheese does neither use, nor even check, the left mouse button
- the left mouse button IS connected to fire, just like vice used to emulate it (and i am right now putting that back into VICE)

really curious now how you came to your conclusions and what exactly you disassembled there :)

edit: ok so... VICE behaves exactly like NEOS mouse now, confirmed with https://sourceforge.net/p/vice-emu/code ... ouse/neos/ (c64 test code) and https://sourceforge.net/p/vice-emu/code ... use/vic20/ (slightly modified version of your vic20 code)

cheers!

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Sat Aug 12, 2017 7:05 am
by polluks
How about a cc65 driver? :idea:

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Mon Aug 21, 2017 8:48 am
by plbyrd
polluks wrote:How about a cc65 driver? :idea:
I started a joystick mouse driver for cc65 last night. Ran into a problem getting it compiled with the standard makefile, have sent an email to the cc65-devel mailing list with the details.

If I get that working then I'll take a look at this code and see about adapting it for VICE. The driver model is pretty simple.

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Fri Aug 03, 2018 1:39 am
by Kakemoms
Links updated (in first two posts)

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Fri Aug 03, 2018 1:54 am
by Kakemoms
groepaz wrote:i have a NEOS mouse here now....and i can tell two things for sure:

- mouse cheese does neither use, nor even check, the left mouse button
- the left mouse button IS connected to fire, just like vice used to emulate it (and i am right now putting that back into VICE)

really curious now how you came to your conclusions and what exactly you disassembled there :)

edit: ok so... VICE behaves exactly like NEOS mouse now, confirmed with https://sourceforge.net/p/vice-emu/code ... ouse/neos/ (c64 test code) and https://sourceforge.net/p/vice-emu/code ... use/vic20/ (slightly modified version of your vic20 code)

cheers!
Thinking back on this I am really sure now that I opened the NEOS mouse to see that the fire button was connected to the left mouse button.

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Fri May 19, 2023 5:17 pm
by javierglez
This is interesting. But I was unable to run the sample programs in VICE.
The program displaying the mouse coordinates shows both values incrementing regardless of the device selection in the Control port box.
Maybe I missed some step or something has changed in the emulator.

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Tue Jun 27, 2023 3:07 pm
by javierglez
I wasn't capturing the mouse Alt-M, however, it still doesn't work. The values stop increasing but then remain constant.
However, I got a real Neos mouse from ebay and sometimes it works fine, sometimes it just does the increasing coordinates thing.
Anyway, it's cool.

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Wed Jun 28, 2023 10:33 am
by groepaz
I think you'll have to make sure to plug in the mouse before turning on the computer, and also make sure nothing else uses that joystickport before you run the NEOS program.... its really all a bit unstable

Re: Vic-20 mouse driver & demo program for NEOS mouse

Posted: Tue Jul 04, 2023 2:30 am
by javierglez
An update about my Neos mouse: it seems to work well with my Final Expansion Alpha plugged in.
Whileas the other day when I was trying it with MCES 37kB RAM (which overlaps IO area) the mouse driver sometimes started fine, but sometimes refused to start and showed the wrong behaviour I tried to explain.