Welcome, Guest. Please login or register.

Author Topic: Cocolino driver, anyone?  (Read 5457 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Thomas

Re: Cocolino driver, anyone?
« on: February 14, 2010, 09:56:51 PM »
FreeWheel does not work without cocolino.driver.

Offline Thomas

Re: Cocolino driver, anyone?
« Reply #1 on: February 15, 2010, 08:25:19 AM »
Quote from: Kronos;543211
What does freewheel do ? Well it boils down to the adapter sending pulses over the middle-button input and freewheel decoding them to up or down movements.


No, FreeWheel does nothing like this. What you describe is exactly what cocolino.driver or in your case the Micromys driver does.

FreeWheel is a commodity, not a driver. It translates one kind of input events (mouse wheel movements) into another kind of input events (cursor up/down keys and scroll bar movements).

If there is no hardware driver which feeds wheel movements into the input stream, FreeWheel has nothing to translate and therefore does nothing.

Bye,
Thomas

Offline Thomas

Re: Cocolino driver, anyone?
« Reply #2 on: February 16, 2010, 03:04:25 PM »
Quote
when I run newmouse


NewMouse is a driver for serial mice. It is completely unrelated to the Cocolino and does nothing for it.

Quote
the middlebutton works, but the scrollwheel doesnt


The middle button should work without any driver already. The scroll wheel only works with cocolino.driver running.


Quote
I've tried Freewheel aswell, but it gave very weird results, selecting text, flicking screens, stuff like that.


This shouldn't happen. In fact you need FreeWheel to get any benefit from the scroll wheel. Without it, only very few applications support the wheel. AWeb for example.

Offline Thomas

Re: Cocolino driver, anyone?
« Reply #3 on: February 16, 2010, 07:08:07 PM »
Quote from: rvo_nl;543508
right, I guess the statements on various websites concerning newmouse and the cocolino.driver are somewhat confusing. at least they confused me aswell:
 
The input events generated by Cocolino.driver are compliant with the format used by the NewMouse program (by Alessandro Zummo). This ensures full compatibility with all the existing wheel-support software.



The Author of NewMouse (Alessandro Zummo) has defined a method how to feed mouse wheel movements into the input event stream of AmigaOS. This method has become a standard because all other drivers like cocolino.driver now use the same method.

So programs like AWeb, DirectoryOpus Magellan and FreeWheel, which support NewMouse, will also work with cocolino.driver.

This is what the statement means.

Offline Thomas

Re: Cocolino driver, anyone?
« Reply #4 on: February 16, 2010, 09:02:54 PM »
Quote
* using freewheel AND newmouse makes no sense *

correct?


No. NewMouse is for serial mice what cocolino.driver is for the Cocolino. FreeWheel is needed in both cases.

If you have a Cocolino, you need cocolino.driver. If you have a serial mouse connected to the serial port, you need NewMouse. If you have both mice, you need both drivers. FreeWheel is needed in any case.


Quote
then I'm afraid my mouse is not entirely compatible with the cocolino driver,


This might or might not be the case. Do you connect the mouse directly to the Cocolino or through a KVM switch ? If you use a KVM switch you should make sure that the Amiga is the first computer which is powered up and the KVM should be switched to the Amiga when the Amiga is powered up.


Quote
or freewheel.


A mouse cannot be incompatible with FreeWheel. FreeWheel does nothing with the mouse. It just translates input events. If there are no events, it does nothing. The driver is responsible to create the events, not FreeWheel.