Multi Commander > Support and Feedback

Quick Search + Search Field - numbers only

<< < (2/3) > >>

Mathias (Author):
Very strange.

Only reason a character is not added to the quicksearch is because if the it does not find the file/folder starting with that letter
of if the character is invalid. But normal 0-9 letters are valid. So not sure why that does not work for you. It should.


There is no different with portable. it is the same executable.. Only difference is default configuration.

Mathias (Author):
There will be a new Beta later today/tomorrow.. (Build 1912 or more )
Upgrade to that then enabled debug logging in
Menu > Configuration > Core Settings > Logging (TAB)
Under Application Log set "Log Level" to "Debug" And press Apply.
Then Press Ctrl+L to show log panel.

Now all the quicksearch keys will be logged to this window and it might be possible to see why it fails

jpavel76:
Thanks Mathias. I tested the beta on my private PC. The problem really comes with the language/keyboard - I probably didn't change it well before.
Attached is a log from US keyboard layout and CZ keyboard layout. In both cases I pressed sequence 090318 on the numeric pad (working with windows snipping tool didn't capture the search field)

Normally the numeric pad is not affected by national characters and I am normally typing only numbers with it, but the initial zero "0" is in the log translated as "é", which lays really on zero, but only on the main keyboard, never on numpad. Looks like MC is treating key from numpad same as equivalent key on main board (Vkey 48-233) for the initial keypress.

On second press when search field is focused all works normally.

Do you think it is possible to fix the behavior, because US keyboard is not an option for me ;) For testing you can set any CS Czech keyboard layout, or i will support as much as I can.

Thank you, Jan.

Mathias (Author):
So CZ layout do not have the number keys as the default character for the 1-9 on the keyboard.
This is why it does not work.
MC get what keyboard key was pressed. and then it translates that to what character that is by asking the keyboard layout.
Numkeys are because of other issues translated to the normal 0-9 before the conversion. That why numkeys not works either.

Not sure if there is a easy fix for this.

jpavel76:
Hello Mathias,
I understand, if is is not possible I will learn to live with it :) In any case I am really glad for this great product.
Jan.

Navigation

[0] Message Index

[#] Next page

[*] Previous page