[Kde-hci] What's This help -> Once more ;-)
Olaf Jan Schmidt
ojschmidt at kde.org
Mon Jan 23 01:07:30 CET 2006
In the meantime I have had some time to think about the most consistent way
for the keyboard focus.
In KDE (and in all other systems that I know of) the tab sequence never leaves
the window. In some cases, it is even limited to a part of the window (e.g.
Kontact). Whenever several windows are involved, they are either all added to
the window list as full windows, or only one of the windows accepts keyboard
focus (e.g. a dialog that blocks the parent window, or a floating toolbar
that doesn't accept keyboard focus). For this reason I suggest that the WT
windows should be behave like normal windows, maybe with a changed look, and
appear in the window list. The focus can then be moved between the windows by
To be consistent with the rest of KDE, the operator window should behave like
other floating toolbars and not accept keyboard focus (unless we define a
general shortcut for this in KDE, which seems like a good idea to me). To
make all actions keyboard reachable, they should be added to the context menu
of all tips.
Usually, a normal keypress does change the focus in another window or move the
focus into another window (unless it closes the current window), so I suggest
the following for Escape:
- Focus on a Tip: Tips disappear. Focus moves back to where it was in the
parent window before the WT mode was activated.
- Focus on a WT window: WT window is closed. Tips remain. Focus moves back to
the currently focused tip in the parent window.
> --> argh, I just realised that my OOo file is broken :-|
> hopefully kword can import the pdf...
Did you have luck?
Olaf Jan Schmidt, KDE Accessibility co-maintainer, open standards
accessibility networker, Protestant theology student and webmaster of
http://accessibility.kde.org/ and http://www.amen-online.de/
More information about the Kde-usability-devel