Correct, you reversed the mapping from function=key to key=function. I already wanted to mention that in my previous post. It might be counter-intuitive at first to assign a function to a key instead of a key to a function, but that's the way I will go also in the GUI: first select the key, then choose the function.cajhin wrote:A custom ini might look like
[key]=[id] [label] ( [explanation] )
F5=86 Refresh Tree (updates the content blah)
Ctrl+R=86 Refresh Tree (second shortcut for f86)
=87 Refresh File List (blah blah)
=88 Reload key map (bb)
About performance: yes, you are probably right. But I have an irrational fixation on speed, so I'll go the fastest way even if nobody notes it.
1: Yep, that's what I wanted to say.cajhin wrote:For the function identifier, I would only use a label (like 'refresh_tree'), not the full path from the GUI. Why? Sometimes you have to rearrange a menu, that's common; but it is generally a bad idea to rename items, so the item names / labels are usually much more stable.
An option: use the number IDs in the ini, too. Provide the item name / GUI label only as a hint for the user. Now you can rename functions without breaking the key mapping.
2: Yep again.
XYplorer Beta Club
