Numeric keypad enter key randomly unbinds

[Peter Steinberg]

SlickEdit Pro 2019 (v24.0.2.0 64-bit), 64-bit Windows 10.

The enter key on the numeric keypad normally works like the regular enter key.

After editing for a while suddenly I start getting the "Key not defined" message when I press the numeric keypad enter key.

The numeric keypad enter key also stops working in dialogs (find, etc.), the command line, etc.

This started happening when (or shortly after) I upgraded from 24.0.1 to 24.0.2

Any idea on how to fix this?

[Clark]

Hot fix checked in for this. I found two mistakes which would cause this (dynamic surround and the block_insert_mode command). You're probably hitting the dynamic surround case a lot.

Simple explanation.  For convenience and backward compatibility, SlickEdit (by default) automatically converts KeyPad keys like Enter to their equivalent non KeyPad key variant if there is no binding for the keypad variant. This allows SlickEdit not to have specific bindings for  KeyPad specific keys yet they still work. Also, users can can make a keypad key binding if they want the keypad key to do something different (some users really want this capability).  However, there are cases where this auto keypad mapping feature has to be temporarily turned off. This is where some mistakes were made.

Thanks for posting about this.

[Peter Steinberg]

Thanks for the quick reply; any idea on when the hotfix will be available?

[SlickEdit Support]

PM sent!

[Peter Steinberg]

Thanks, that looks like it has fixed the issue.

[bengle]

Any idea when this fix might be available?  Since this is the Enter key that I always use, it is very annoying.

[SlickEdit Support]

PM sent.

The hotfix will be published shortly at www.slickedit.com/hotfix

Regards,
SlickEdit Support

[dunkers]

Was this in hotfix 5? Prior to applying that I had this issue and it's a right pain. I applied hotfix 5 and the pad enter splits the line (although maybe it won't soon!) but it doesn't auto-indent like the real enter key does.

If the hotfix didn't have this fix in it, could I have a PM too, please? I seem to use the pad enter more than the proper one.

[Clark]

I'm not able to reproduce this difference where one Enter key indents and the other doesn't. What is the language type of the file you are editing. I only tested C++ so far.

[dunkers]

It is C/C++. Checking keybinding, pad enter is bound to split_insert_line(), just like enter.

Perhaps I need to be more specific. Given this code:

Code: [Select]

    if (something) {
    }
with the cursor at the end of the first line, pad enter inserts a blank link and puts the cursor under the if:

Code: [Select]

    if (something) {
    |
    }So that's indenting to the start of the if statement. But enter indents to the beautifier depth, which in this case in a further indent:

Code: [Select]

    if (something) {
        |
    }
I and use both keys in that if() and the indents are consistent and 100% reproducible.

Edit: 24.1 is fine.

[dunkers]

Dunno why I didn't spot this before: the main enter key is bound to TONS of stuff, just one of which is split_insert_line(). Taking a punt I bound pad enter to c-enter and now it works as it should (in C files).

But shouldn't it be bound to all the functions that the big enter is bound to? If so, how come it isn't, and is there a quick (and simple) way to make it so?

[Clark]

If you bind your Pad Enter key, then it can function differently. Otherwise, SlickEdit is supposed to automatically map it onto your regular Enter key binding.

You might want to try a default config. Maybe you bound the Pad Enter key accidentally.

[dunkers]

I don't bind keys, so no chance of that. I just installed 24.2 and let it copy my config from 24.1, which still works as it should. Definitely a 24.2 problems, whether it lost something or didn't copy something.

OK, I just unbound pad enter from everything and now it's back to the original issue: inserts a line and only indents as far as the 'if' in my example above. Or the start column of the previous line. That is, it's ignoring the beautifier settings. Enter works as expected.

[Clark]

Please post your user.cfg.xml. I'll remove any bindings you have for Pad Enter and see if I can reproduce this problem.

[dunkers]

I'd prefer not to post that here since it has client identifiers in it. I tried to send a URL to you where you can download it, but apparently you don't accept PMs (or, at least, not from me). Any other way I can get this to you?