Opened 16 years ago
Closed 16 years ago
#3138 closed bug (fixed)
Mouse works poorly in r28643
Reported by: | Adek336 | Owned by: | stippi |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Mouse/PS2 | Version: | R1/pre-alpha1 |
Keywords: | Cc: | mtr | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
In hrev28643 the mouse started to work poorly: the mouse pointer would move very slowly, large hand movements needed to use the mouse. Changing mouse speed / acceleration in the mouse preflet would cause the mouse to move by big leaps, cannot precisely move the mouse where I'd want to.
Change History (8)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
comment:3 by , 16 years ago
I don't know if this is related, but i tested hrev29417 in VMware Server and the mouse pointer doesn't work fluidly. I suppose (i'm new to Haiku :) ) that the mouse "driver" is MouseInputDevice.cpp. Maybe changing kMouseThreadPriority could hackfix this problem. I tested 28641 too and got the same problem.
Thanks
comment:4 by , 16 years ago
Cc: | added |
---|
comment:5 by , 16 years ago
Owner: | changed from | to
---|
Hi stippi, can you have a look into this issue? Unfortunately I did miss the initial notification 4 month ago.
comment:6 by , 16 years ago
But I thought I turned the synaptics driver off again?! Anyways, Clemens has sent me a patch a long time ago, which I am supposed to check out. The patch basically resets the PS/2 controller after testing if it's a Synaptics controller. The original problem reported in the ticket was that testing for Synaptics seems to modify the behavior of the PS/2 controller which results in this different mouse feeling, even if the Synaptics driver isn't even active.
comment:7 by , 16 years ago
Unless I'm mistaken, the Synaptics driver is now enabled again and here, things work just like before hrev28643 (mouse still doing big leaps when maxing the mouse speed), so I'm happy.
I confirm the balls-achingly slow mouse speed, both in Vmware and real hw. However, the mouse speed/acc settings caused the same pointer behaviour before hrev28643 as well, so that's a different bug, I believe.