RE: Ang. Re: Proposal: mouse-only Caribou for GNOME 2.30
- From: "David Colven" <Colven ace-centre org uk>
- To: "Steve Lee" <steve fullmeasure co uk>
- Cc: gnome-accessibility-list-bounces gnome org, Gnome Accessibility List <gnome-accessibility-list gnome org>
- Subject: RE: Ang. Re: Proposal: mouse-only Caribou for GNOME 2.30
- Date: Fri, 11 Dec 2009 13:39:35 -0000
Glad I keeping some marbles.
I feel what we need - and is part of the ACE contribution to AEGIS - is a central switch handler (control panel type thing) which reads switches and that any scanning program can use. The control panel would deal with all the methods and filtering and pass scan select (and more) to the scanning programs. This would eliminate the need for multiple set-ups and a lot of duplicate effort in reading switch inputs.
David
-----Original Message-----
From: Steve Lee [mailto:steve fullmeasure co uk]
Sent: 11 December 2009 13:36
To: David Colven
Cc: Mats Lundälv; gnome-accessibility-list-bounces gnome org; Gnome Accessibility List
Subject: Re: Ang. Re: Proposal: mouse-only Caribou for GNOME 2.30
2009/12/11 David Colven <Colven ace-centre org uk>:
> Sorry if I'm being dum - I am down with flu at the moment - but I don't see
> why a joystick switch inout should not do exactly what the daisy reader
> wants. Window will not react to input from a USB fire button unless it's
> told to, will ot?
Yes that is exactly correct. AFAIK the foot switch was a USB HID - ie
same as joystick. So the point was that sometimes having events
ignored by the OS can be useful.
Windows doesn't treat joysticks as first class input devices that all
programs must support (like mouse and keyboard). The same with default
X. I'm not familiar enough with the X switch stuff that Willie
mentioned, but get the impression switch events become first class
events so applications including desktop may react. As I said it was
an "aside".
Steve
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]