AW: making fallback access keys configurable
Tobias Anton
tobias at ke.informatik.tu-darmstadt.de
Tue Feb 28 13:55:50 GMT 2006
Well, you could also use the tab key to access the form elements. Anyway,
breaking existing usage patterns in future releases generally is a bad idea
imho. This is also the case if the usage pattern is made configurable and
disabled by default. I mean, a user certainly cannot be supposed to know
what new configuration options have been added.
Tobias
-----Ursprüngliche Nachricht-----
Von: Thiago Macieira [mailto:thiago at kde.org]
Gesendet: Dienstag, 28. Februar 2006 10:30
An: kfm-devel at kde.org
Betreff: Re: making fallback access keys configurable
Aaron J. Seigo wrote:
>i'm sure you've hit CTRL in konqi and seen the billion access keys popup
> up all over the page. better yet is when it happens in kmail ;)
How do you think I manage to read 1000 emails in kde-bugs-dist?
If it weren't for access keys, it would take twice as long... moving the
mouse to click the HTML link, wheeling down to the comment area, typing
comment, selecting the options, clicking Submit.
all I do now is hit Ctrl, H, wait for it to load, Ctrl, C, type comments,
Ctrl, O and it's done.
This feature is really useful to be disabled by default with no GUI for
turning it on, IMHO.
>in future i think it would make sense to add this into the accessibility
> world of kde much as we do with slow keys, etc ....
Agreed. Could this qualify for the string-unfreeze period?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
3. Ac seo woruld wearð geborod, swá se Scieppend cwæð "Gewurde Unix" and
wundor fremede and him "Unix" genemned, þæt is se rihtendgesamnung.
More information about the kfm-devel
mailing list