It also makes sense to me. We could however keep (in addition to F3) the CTRL+F for search window because it is very used in other apps.
If think the toggle fullscreen feature is very used, I wonder if we should not also add a button in the button bar for it?
To change or add new keystrokes, only the .ui files should need to be modified. For the missing ones, new QActions need to be added. This also defines the list of required SLOT to implement.
On 2/26/08, Matthew Gates <email@example.com> wrote:Hi,
I feel that we should make the following changes to the key bindings.
F1 should be for the help window. This is standard for almost all apps on
most platforms.I don't like the control-L key for the location window, and generally using
the control key for dialog shortcuts. I always liked to be able to toggle
the config window using 1 while keeping my other hand on the mouse. I
think a control key combination is less comfortable.
Maybe the F keys would be good for dialogs? Something like
F1 - help
F2 - config
F3 - search
F4 - display options
F5 - calendar / date
F11 - toggle full screen
I like most of the other bindings from 0.9.x. What do you think?
From a windows user standpoint, that list makes a lot of sense. F11 is a traditional fullscreen toggle. Separating the window keys from the buttons on the keyboard like we do in the interface sounds logical.
Some keystrokes don't work in the last svn version. I noticed S doesn't toggle stars for instance.