But this very same thing makes it very awkward who want sticky keys on the keyboard and non-sticky on a physical. Which would be true for all non-a11y users and some a11y users.
In the end though the only manner it interferes with my keyboard is the annoying dialogue that pops up, and the average gnome-ally user will probably be plenty used to seeing annoying dialogs anyway. The slow keys dialogue however is another matter though. Normal operations are not resumed until it is dismissed. Which in itself incredibly annoying. When planning the SOK I wanted to stay away from the three odd dialogs that GOK pops up when it is started. The plain fact is I don't want any dialogs when starting SOK. At all. Using the system wide sticky keys means I need to have at least one dialog box when my keyboard starts and is therefore completely unacceptable. On 26/06/06, Bill Haneman <[EMAIL PROTECTED]> wrote: > On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote: > > Chris Jones wrote: > > > ... > > > > > > In other words I cannot spend the summer making gnome-a11y suitable > > > for my needs. What I need is a temporary work around until after the > > > SoC when I could find time to work on this aspect of gnome-a11y and > > > fix my program so it is not an "accessibility violation". > > Chris, > > > > Can you not simply make SOK remember that shift was pressed and keep the > > state internally in SOK? IOW: > > We tried this with GOK at an early stage and it was not satisfactory. > It also clashed badly with StickyKeys. It doesn't make sense to build > an onscreen keyboard and then not expect disabled users to try and use > it, and they will rightly complain if it conflicts with StickyKeys. > > If you really are unwilling to turn on the global StickyKeys gconf key > while the onscreen keyboard is posted, or at least when the pointer is > inside it... (and I really do not understand why this would be a > problem) there is XKB ABI which you can use to change the latch/lock > status of individual modifier keys. This should do exactly what you > want without making StickyKeys active for the physical keyboard. > > google for XKBlib.pdf to find the XKB client manual, I believe it's > section 10.6 that has the relevant client APIs. > > regards > > Bill > > > 1. when the user clicks shift you set a flag. When a letter is clicked > > SOK sends shift+<letter>+unshift to X and removes the flag. > > > > 2. When shift is clicked twice you set a sticky flag. Again, each time > > the user clicks a letter, SOK sends shift+<letter>+unshift. When shift > > is clicked again you unset the flag. > > > > That way you avoid triggering slow keys and avoid making an > > 'accessibility violation'. > > > > Bill, is it an accessibility violation to have unusable accessibility tools? > > > > - Henrik > > > > _______________________________________________ > > gnome-accessibility-list mailing list > > gnome-accessibility-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > > -- Chris Jones jabber - [EMAIL PROTECTED] msn - [EMAIL PROTECTED] _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
