When you write applications, it is important to include both the CUA and the Windows/Apple keyboard shortcuts, and get the tab order of keyboard accessible user elements right.
Many modern applications seem to put less and less emphasis on the most efficient user input device: the keyboard.
You should: it makes your application much more pleasant to use.
I wrote about CUA before, but the Windows and Mac shortcuts are just as important.
A small table (please post a comment if you know additions):
| Function | CUA | Windows | Mac |
|---|---|---|---|
| Copy | Ctrl + Insert | Ctrl + C | Command + C |
| Cut | Shift + Delete | Ctrl + X | Command + X |
| Paste | Shift + Insert | Ctrl + V | Command + V |
| Delete before cursor | Backspace | Delete | |
| Delete after cursor | Delete | Fn + Delete | |
| Undo | Alt + Backspace | Ctrl + Z | Command + Z |
| Redo | Ctrl + Y | Command + Y | |
| Confirm the current task | Enter | Return | |
| Cancel the current task | Escape | Escape | |
| Next field | Tab | Tab | |
| Previous field | Shift + Tab | Shift + Tab | |
| Next pane | Ctrl + F6 | ||
| Previous pane | Alt + F6 | ||
| Next window | F6 | Cmd + ` | |
| Previous window | Shift + F6 | ||
| Application menu | Alt + Space | ||
| Windows menu | ⊞ | ||
| Local menu | Shift + F10 | Local Menu |
Note that many Linux programs follow both the CUA and Windows settings.
References:
- CUA: SAA Common User Access Bookshelf
- Windows: Guidelines for Keyboard User Interface Design
- HIG: Keyboard Shortcuts
–jeroen
The Wiert Corner - irregular stream of stuff 