Hi!

3-Янв-2008 13:21 [EMAIL PROTECTED] (Alain M.) wrote to
freedos-devel@lists.sourceforge.net:

>> In that case, you probably want "disable wheel" to be the
>> default, too, as disabling the wheel improves compatibility
>> quite a bit.
AM> I 100% agree.

     I think, this is important only for PS2, where wheel support is dumb
and unreliable. In serial protocols (MS+wheel, LT) disabling wheel gives
nothing.

AM> The proble is two fold: first it causes compatibility
AM> problems, sencond there is *very* few programs around that would use it
AM> anyway and it would be logical that *these* programs have instructions
AM> to activate it.

     Alain, talking about disabling/enabling through command line
completely, API doesn't have (yet?) functions to enable wheel support.

>> So the above 3 types "talk Microsoft" unless you press or release
AM> YES i have made it for 1.6b, all MS Logitech are intercangeable on the
AM> fly. I still use that version because all my improvements were
AM> disregarded :(

     Not all. :) But code of handlers was hardly changed in those times,
and there was also target to minimize resident part size as much, as
possible, whereas "autoswitch" may have own side effects. For example, with
autoswicth we not know (can't know) how much buttons currently attached
mouse have or if current mouse have wheel or not, and this makes useless
checking BX after INT 33/0000 (should always contain 3 for serial mice) or
bit 0 of CX after INT33/11 (will/should always be set). And, if some app
wish to change its behavior depending on presence 3rd button/wheel in mouse,
then such app's behavior change will be invalid if there attached
2-button/non-wheel mouse.

>>> "auto decision" may cause "mystic" middle button state changes
>>> and wheel rotations. I remember, there WAS some troubles with
>>> middle button in my initial experiments (or this was troubles
>>> with MSM protocol? don't remember precisely...).
AM> What I can tell is that Cutemouse 1.6b can use ANY serial mouse and
AM> switch ON THE FLY from ANY serial mouse to ANY other mouse.

     Including MSys? I remember we discuss reinitializing UART for different
speed (this need, there is no possibility in general to work with some
common speed for MSys and LT/MS protocols).

AM> 100% tested
AM> in the field what serial mice where commmon.

>> releasing it once to get the driver back in sync. But maybe
>> there are other protocols where for example "LR encodes a M
>> toggle" is used to get along with only 3 bytes...?

     No. There was idea for it support, but it was excluded after some
testing.

AM> remember that changing mice qas

     "qas"?

AM> very common before the advent of modern
AM> optical ball-less mice.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to