Re: Re: Design for Keyboard Shortcut Behaviour
Rogelio Serrano <[email protected]>
| Newsgroups | gmane.comp.graphics.y.devel |
|---|---|
| Message-ID | <138adf55d8567c8f3da891b199dc7cec@debian> |
On 2004-05-25 18:26:54 +0800 Andrew Suffield <[email protected]> wrote: > On Mon, May 24, 2004 at 03:09:49PM +0300, Mikko Rantalainen > wrote: >>> | | shutdown : Shut down computer | | >> >> Have you tried to hold down the windows key and type >> "shutdown" in the same >> time? That's far from a good UI! I'll call the windows key >> COMMAND key from >> this on so it can refer to any key one wishes to use for that. > > Please don't use meta-names that actually exist as real > keys. Macintosh keyboards have 'command' keys. > >> By this, it should be clear that user should be allowed to >> customize this >> menu. It could be that you start Mozilla once a week (and >> keep it running >> for the rest of the week) while another user starts and stops >> Mozilla every >> 15 minutes. For the latter user it's much more important to >> have only a few >> keypresses for the shortcut. > > "We're so far ahead of you that you can't even see the > tracks". More > on this later. > >>> released. In existing interfaces pressing [ctrl]-x to cut >>> takes effect >>> >immediately the x key is depressed, and new commands can >>> now be entered >>> >without first releasing the [ctrl] key (although 'alt-tab' >>> behavious in >>> >existing systems breaks this rule, only taking effect when >>> [alt] is >>> >released) >> >> I think that the CTRL key should work like it's working right >> now. > > Well, right now it doesn't work at all. I've only got as far > as ISO > 9995-3, not CUA events. > I removed the windows key from my keyboard. The caps lock too. Cant we just keep the keyboard simple?