Forward keys to commandline bar - PageUp/Home

[mardukchan]

Hello,
I have problem with checked on Explorer Panel Settings - Keyboard handling - Forward keys to commandline bar. This is very usefull feature, but when it is on, then cursor (sometimes) jumps into bar when I press PageUp or Home (may be on some others keys). I think, that cursor should jump into command line when characters are pressed only (for quick search I use Alt+key). Can you fix this?

Thanks, Marek

[Mathias (Author)]

I don't know how you manage to do that.
PgUp/PgDn are hard wired to move the focus item a page up / down. And that key is never handled as unhandled and are not sent to the commandline field.
Do you have some unusual keyboard setup or something else that can change it ?
Do you use a laptop keyboard or some other mini keyboard that uses multiple keys on the same key ?

[mardukchan]

I have no special settings. I found, that it happens when I use Up/Down keys too. When I browse dirs/files and I press repeatedly Up (or Down) key (approx. 12x), then the command line sets focus, cursor skips there and Up/Down browse history of commands. When I uncheck Forward keys to commandline bar in settings, then the command line never gets focus, but I can't simple type commands (I have to click into commandline with mouse).

Thanks, Marek

[Mathias (Author)]

Strange. 
Something else must be causing it, because it does not make sense.

I looked at the code and pagedn/pageup can not be forwarded to the commandline field because those key are never reached the part the forward the keys.

Also the part that forward keys to the commandline field block all special keys from being forwarded.  and pageup/pagedown and the arrow keys are among them.
So some other key must be triggering it or something.

[Mathias (Author)]

If you enable the Application Log with log level "debug" under Core Settings in the latest beta version.. (build 1629+) it will log what key that is triggering forwarding.

[mardukchan]

Hello,
here are results from log. Only UP/DOWN keys were pressed (randomly forwarded key bellow and cursor skipped to command line bar):

2014-02-22 16:32:26.729 Forwarding key : 0xff , Rep 1 , Flags : 0x4159
2014-02-22 16:32:34.239 Forwarding key : 0xff , Rep 1 , Flags : 0x4159
2014-02-22 16:32:41.256 Forwarding key : 0xff , Rep 1 , Flags : 0x4159

[Mathias (Author)]

Key 0xff is not the up/down key.  0xff is often sent if yo also have to hold the the "Fn" key when pressing the key.. (used on Laptop or mini keyboards.)
Why it is sent for a normal keyboard I do not know. It should not.

[mardukchan]

Hello,
I found this:

Command ff: Keyboard reset
Reset and self-test. The self-test (BAT) will return aa when OK, and fc otherwise. As part of the self-test, all LEDs are flashed.

I have Microsoft Wireless Multimedia Keyboard and Windows 8.1.

Is it possible to ignore this keycode in Multi Commander (hard or in config)?

Thanks, Marek

[Mathias (Author)]

Not sure that is the same 0xff code. That looks like the hardware code. Windows will send a virtual key code to application. And it is that, that is 0xff.

Maybe MC can ignore 0xff in the future, problem is that some Fn+<key> combination is also sending that key code and then it should not be blocked.

[mardukchan]

Hi, I tried latest beta (build 1640) and it seems that the problem is gone. Great work.
Marek

[Mathias (Author)]

It might be a temporary fix only. The fix might have side effect with other key combination.. and then it might need to be removed again..
But time will tell..