[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
from the Platform SDK (mouse_event function)
please read carefully
Relative mouse motion is subject to the effects of the mouse speed and the
two mouse threshold values. In Windows NT, an end user sets these three
values with the Mouse Tracking Speed slider of Control Panel's Mouse option;
in Windows 95, an end user sets them with the Pointer Speed slider of the
Control Panel's Mouse property sheet. An application obtains and sets these
values with the SystemParametersInfo function.
The operating system applies two tests to the specified relative mouse
motion. If the specified distance along either the x or y axis is greater
than the first mouse threshold value, and the mouse speed is not zero, the
operating system doubles the distance. If the specified distance along
either the x or y axis is greater than the second mouse threshold value, and
the mouse speed is equal to two, the operating system doubles the distance
that resulted from applying the first threshold test. It is thus possible
for the operating system to multiply relatively-specified mouse motion along
the x or y axis by up to four times.
Now, there are 2 solutions to the problem of slow at fullscreen:
do you think we should
1) add this last part to the actual DirectInput driver used in full screen
or
2) should we use GetCursorPos to get the mouse cursor pos and
SystemParametersInfo to change the speed and then restore it when switching
out?
Also, in windowed mode:
should the mouse speed be able to change in that mode?
seems right that when you select a region and you get out of it it restores
the windows cursor no matter if you are out of the allegro mouse region BUT
still inside the allegro window?
Thanks in advance!