From: wisher AT ms6 DOT hinet DOT net (Wisher)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro - Mouse Problems
Date: Sat, 09 Aug 1997 08:29:43 GMT
Organization: The Wisher
Lines: 28
Message-ID: <33ec29e8.7743012@netnews.hinet.net>
References: <01bca110$a1ac3ee0$234747c3 AT 486> <33e90e00 DOT 362572 AT netnews DOT hinet DOT net> <01bca373$0e1bca00$1a4747c3 AT 486> <33ea8cf0 DOT 36291792 AT netnews DOT hinet DOT net> <33EACB68 DOT 25FE AT oce DOT nl> <33eaf801 DOT 4810496 AT netnews DOT hinet DOT net> <33ec086f DOT 3037182 AT news DOT netvision DOT net DOT il>
NNTP-Posting-Host: h15.s155.ts.hinet.net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Sat, 09 Aug 1997 06:05:28 GMT, you wrote:
>hi,
>i have a non-logi mouse which acts just like that in grabber.

Do you mean that your non-Logitech mouse would move in 2, 4 or 8
increments in SVGA modes with the temporary-DIRTY-Fix? 
If so, it's 'normal', I guess.
Because mouse drivers would return that kind of values in SVGA modes.
That's why Allegro would adjust the values by the factor of 8. The
dirty-fix just remove this adjustment to speed-up the Logitech mouse.
So, all(?) mice should act this snap-to-grid way with the fix.
To let other non-Logitech mice live with the dirty-fix, you have to do
this before calling install_mouse():
    MOUSE_ADJUST = 8;
Or, if you won't bump into Logitech mouse very often, forget the
dirty-fix, or keep it but in the 'mouse.c' file change the fixed-line:
    int MOUSE_ADJUST = 1; // initial value for Logitech mouse
to
    int MOUSE_ADJUST = 8; // initial value for Non-Logitech mouse
And set the value to 1 before calling install_mouse() when you meet
one Logitech mouse.

Or, do you mean that your non-Logitech mouse is also very slow with
the original library?
Hope not. If so, Shawn might be interested to know the name of your
mouse.

Thansk for your information & Happy Coding!