[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Pressing unconfigured key
From:       Maciej Pilichowski <bluedzins () wp ! pl>
Date:       2009-05-27 10:41:53
Message-ID: 200905271241.53439.bluedzins () wp ! pl
[Download RAW message or body]

On Wednesday 27 May 2009 12:27:02 Anne Wilson wrote:

> > Sorry but that doesn't make sense. If the user doesn't hit
> > unrecognized keys, then this feature isn't visible.
>
> Exactly.  So if you rarely hit such a key it is not going to annoy
> you :-)

Does really KDE has to be minefield? Currently I am safe with every 
mistake because nothing happens, so I don't care -- I have time to 
correct myself.

But with proposed change it will be more "boo, you missed F8".

> > And if this has a "never again" checkbox, does this checkbox
> > disable this feature completely, or just for the key that has
> > been pressed to bring it up.
>
> Definitely for that key only.  

? But if you hit another unmapped key, new question to answer? 

Do you want map alt+f12 now?
Do you want to map ctrl+alf+shift+f3 now?
Do you want...

Did you try MS Office with Assistant on? It was the great lesson and 
users reaction to it shows us how they feel with forced decisions.

> > The latter would mean its still highly annoying, especially when
> > apps that usually map global shortcuts to the keys are not
> > started (for example no browser open, so nothing maps the
> > Forward/Backward buttons).
>
> Sorry, I don't understand what you are saying here.  Things like
> forward and backward, volume up/down etc. are usually mapped in the
> distros.  

Skip to the next track. No Amarok no mapped key.

Do you want to map... ?

Cheers,
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]