Suggestion:
When redefine hotkeys in configuration dialog, show the default commands instead of "Default command (no remapping)".
This way user would be easier to know wether a hotkey is occupied by default settings.
For example, when define Ctrl+F1, show something like
"[Default]cm_SrcShort"
or
"*cm_SrcShort (Source: Only file names)" and add a little comment below saying "commands with leading * is defined by default"
[Suggestion]Show default hotkeys in config
Moderators: white, Hacker, petermad, Stefan2
-
SanskritFritz
- Power Member
- Posts: 3693
- Joined: 2003-07-24, 09:25 UTC
- Location: Budapest, Hungary
-
Balderstrom
- Power Member
- Posts: 2148
- Joined: 2005-10-11, 10:10 UTC
-
StickyNomad
- Power Member
- Posts: 1933
- Joined: 2004-01-10, 00:15 UTC
- Location: Germany
-
ghisler(Author)
- Site Admin
- Posts: 48088
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
It would indeed be nice, but neither I nor Total Commander have an overview of the key mapping! Why? For some hotkeys, I don't check if a specific modifier key (Shift, Ctrl, Alt) is pressed or not, because it's not relevant. So the command may actually work with two or more hotkeys, although only one is defined.
When I added custom hotkeys, I had to decide whether I wanted to leave it this way, or define all hotkeys via the same custom table. I decided not to change it, because many users may be using these unwanted hotkeys, and would have to learn other hotkeys.
When I added custom hotkeys, I had to decide whether I wanted to leave it this way, or define all hotkeys via the same custom table. I decided not to change it, because many users may be using these unwanted hotkeys, and would have to learn other hotkeys.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
From my point of view this suggestion is good based on the current hotkey management. The problem is that the current hotkey management is almost unusable. A suggestion based on such a system doesn't make sense.
I never heard a user saying: "Ah Ctrl+G! Let's assign another command to it." It works vica-versa. Choose a command first then choose a desired hotkey.
This approach requires a hotkey conflict handling performed by TC but thousands of other programs are able to do this...
I never heard a user saying: "Ah Ctrl+G! Let's assign another command to it." It works vica-versa. Choose a command first then choose a desired hotkey.
This approach requires a hotkey conflict handling performed by TC but thousands of other programs are able to do this...
-
majkinetor !
- Power Member
- Posts: 1580
- Joined: 2006-01-18, 07:56 UTC
- Contact:
-
Balderstrom
- Power Member
- Posts: 2148
- Joined: 2005-10-11, 10:10 UTC
So instead of fixing a flaw||bad behaviour, leave it in a convoluted state just so a couple people that have gotten used to the bad behaviour of hotKeys aren't inconvenienced.
So if we want hotKeys to function properly we have to go use something like AHK and define them all in there.
Makes sense eh?
So if we want hotKeys to function properly we have to go use something like AHK and define them all in there.
Makes sense eh?
*BLINK* TC9 Added WM_COPYDATA and WM_USER queries for scripting.
2ghisler(Author)
We should anyone press Alt+Shift-F10 instead of Alt+F10 to display the directory tree (beside the user has defined it explicitely)?I don't check if a specific modifier key (Shift, Ctrl, Alt) is pressed or not, because it's not relevant. So the command may actually work with two or more hotkeys, although only one is defined.
When I added custom hotkeys, I had to decide whether I wanted to leave it this way, or define all hotkeys via the same custom table. I decided not to change it, because many users may be using these unwanted hotkeys, and would have to learn other hotkeys.