[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Mouse Locking
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Tue, 19 Oct 2004 17:50:32 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=O+Cc22X953cdsDgQs7qZRHji5Sj4l+EFEe+GM1D3AHDKkD+G84rcRZTJR4ar4miSio6mfJnfn1P/dZ/WKCBhIBNlt2bUGZ03Amak3gD6KN1YjDuT3/qFWKhQxq/9bKv00/gsR2rAhNJ0ZyJopEUQWTYhs+/YuO3N0wTKEzb14LM
On Wed, 20 Oct 2004 02:30:13 +0200, Elias Pschernig <allefant@xxxxxxxxxx> wrote:
> >
> > Anyway, what im thinking is an additional two
> > functions in the API, lock_mouse(), and
> > release_mouse(). What do you guys think of the idea?
> >
>
> I think it's a good idea. And instead of just the window, it should
> be combined with set_mouse_range.
Yes, though my method would be having the software mouse enabled would
lock the mouse to the window (since we may have to do mouse warping
anyway), which you could disable by enabling the hardware mouse (even
if the hardware mouse isn't avialble, it'd still allow the mouse to
leave the window then). I still don't think many Allegro programs are
designed for windowed mode where the mouse is free to leave the
window, and the ones that do work already contain hacks that wouldn't
interfere (calling set_mouse_position regularly). The only apps that
would be ok with the mouse leaving are GUI apps, and we can make some
kind of special-case for that (or implicitly enable the hardware mouse
there).
- Kitty Cat