| Re: [AD] Using system mouse cursor |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Wednesday 22 September 2004 03:33, Chris wrote:
> I'm still not sure about the behavior of the patch. It still seems to
> have conditional mouse warping when the hardware cursor is disabled,
> which can cause problems with thew mouse getting out of the window.
This is just the current Allegro (WIP 4.1.15) behavior - in other words,
the patch changes nothing if the software cursor is in use. Redesigning
that is IMO a seperate issue from adding the hardware cursor. (As in, it's
easier to keep my local tree clean if I don't clutter it with too much
unapplied and redesigned code ;))
> IMO,
> the mouse should be unable to leave the app area when the hardware mouse
> is disabled, otherwise you run the risk of the mouse leaving the window
> and failing to get mickeys. The hardware mouse should move as little as
> possible when the software mouse is enabled.
Then, if the software cursor is in use by default, you have an ill-behaved
windowed application. This would only be possible, I think, if the
software cursor is not the default cursor.
> Also, I think the GUI
> should automatically try to enable the hardware cursor, if the cursor is
> set to show on the screen/a video bitmap.
Possibly - although I'm not sure if some GUI based applications doesn't
check mouse mickeys from a custom procedure.
> I think this will only happen if it's called repeatedly, with less than
> 10ms between calls (which is the speed of the input thread, which will
> force a flush of the queue for the new thread/context).
Ok. Limiting the amount of time between warps could still be a good idea
though.
Evert