PrusaSlicer 2.8.0 does not accept input from keyboard numeric row (mainly `-`)

[sharky98]

Description of the bug

When entering values in a field, the negative symbol - (U+002D HYPHEN-MINUS character) when entered from the numeric row (scancode 0c) is not considered by PrusaSlicer. Using the numpad substraction symbol (scancode 4a), which is also the - (U+002D HYPHEN-MINUS character) symbol, does work.

So far, I was not able to use the -, scancode 0c in any input (search bar, translation, rotation, settings, renaming an object, etc.).

The key = is also ignored in my case.

There seems to have a recurring pattern with various affected key, but the negative sign seems to be common for all reported cases I was able to find: #12939, #12988, #12985, #12961, #13019. #13023 may also be related as the user mention that the numeric row + does not work.

Project file & How to reproduce

1. Focus in any text or numeric field.
2. Use the numeric row -.
3. See no input.

empty-project.zip

Using the on-screen keyboard to demo the behavior.

Recording.2024-07-07.230625.mp4

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

Version 2.8.0+win64

Operating system

Windows 11 & Windows 10

Printer model

Ender 3 S1 Pro

[lukasmatena]

Thanks for the report and the list of duplicates.
We willl look into it. SPE-2408

[themanyone]

I would volunteer to help. But I can not reproduce this on Linux. And do not have th' resources to test Windows.

Although not a source of trusted code, AI is good at associating tokens to find popular ideas to try. The following excerpt from claude.ai might prove helpful.

------ claude.ai chat -------

themanyone: Any clue what might be intercepting the keyboard and preventing typing '-' key on WIN32?

claude: If the '-' key is not working on a Windows system, especially in a wxWidgets application, there could be several reasons for this. Here are some possibilities and ways to investigate:

Global Hotkeys: Some applications or system utilities might be capturing the '-' key globally. Check if the key works in other applications.
Keyboard Layout: Ensure that the correct keyboard layout is selected in Windows settings.
wxWidgets Event Handling: Your application might be inadvertently capturing or stopping the propagation of the '-' key event. To investigate this:
Implement a wxEVT_CHAR_HOOK handler in your main frame or the problematic window:

void MyFrame::OnCharHook(wxKeyEvent& event)
{
    wxLogDebug("Key pressed: %d", event.GetKeyCode());
    event.Skip();
}

Bind this handler:

     this->Bind(wxEVT_CHAR_HOOK, &MyFrame::OnCharHook, this);

This will log all key presses, allowing you to see if the '-' key event is being received.
Focus Issues: The '-' key might not work if the focus is on a control that doesn't accept it. Ensure the focus is on the correct control when you're trying to type '-'.
Custom Event Handlers: Check if you have any custom event handlers that might be intercepting keyboard events.
Accelerator Tables: Review your accelerator tables to ensure '-' isn't being used as a shortcut.
Input Method Editors (IMEs): If you're using an IME, it might be intercepting certain keystrokes. Try disabling the IME temporarily.
Windows API Hooking: Some applications use low-level keyboard hooks. You can use tools like Process Monitor to see if any processes are hooking keyboard input.
Accessibility Features: Certain Windows accessibility features can interfere with keyboard input. Check if any such features are enabled.
Hardware Issues: Although unlikely if it's just the '-' key, it's worth checking if the key works in other applications or on the Windows on-screen keyboard.

To further diagnose the issue, you could implement a more detailed logging system for key events in your application. This would help you understand at what level the key press is being lost or intercepted.

If you can provide more context about where in your application this is occurring (e.g., in a specific text control, globally across the app), I can offer more targeted advice over at claude.ai

[Dycus]

I'm also having this issue on Prusaslicer 2.8.0 on 64-bit Windows 10.
I'm unable to type "-" or "=" from the numeric row in any non-dialogue-box text field I can find in the slicer. All other keys work, including"_", "+", and "-" on the numpad.

I can't type -/= in print settings fields, notes fields, gcode fields, etc. But if I click to save a preset, a dialogue box pops up, and I can type them there.

Pasting the characters does work in all fields.

[Murder-exe]

Win11 64 bit:

• ad minus
  Won't allow me to enter symbol "-" when using English language with keyboard Czech (QUERTY), but it works when I switch to English language with keyboard US. Both using in-build laptop keyboard.
• ad 1
  It is exactly opposite way = US keybard doesn't type the char to input field but Czech (QUERTY) does.

[karacaenes]

win 11, same issue but can't enter "4" anywhere. (i.e. any of the print settings number boxes). Very annoying while using 0.4 nozzle. I can copy a 4 and paste it to places i can't enter with keyboard though. (also, i do not have a numpad on my keyboard, standard number row "4" and "-" do not work.