Terminal.Gui
Terminal.Gui copied to clipboard
Numpad symbols are not printing on screen
If I print the numbers and symbols from [0-9] and [/*-+.] on the keys in the letters area everything is working fine. If I try to do the same with the keys in the numpad area the symbols that are not numbers don't show.
OS: Windows 10 x64 2004 (19041.685) GUI.cs version: latest from repo (92c2171388918bb4d9a96f2eec7a0158aee029bc)
It might be related to bug: https://github.com/migueldeicaza/gui.cs/issues/977

My keyboard configuration:

The two keys tested:
Numpad:
Above letters:

If you are running on Linux on a virtual machine it really happens.
It is not a VM. I updated relevant information in my first comment.
I'm also using Windows 10 and that doesn´t happens to me.
You are using the same keyboard configuration?
No but I think that doesn't have to do with keyboard configuration. Try the last version in the GUI master to check if it still happens.
I am working with the latest from the master as I specified in my comment. The version I specified is not the latest? If not then please send me the sha-1 of the commit you want me to checkout.
I just tested again in my code and I found out that it started to work in my program but still doesn't work in the samples for some reason.
Sorry my bad. I didn't realize you mean about the Reactive example. Yes I confirm that not working on the NumPad.
Can you see the reason please, because I'm not familiar with that language.
I don't know if that behavior is because the project is using the NuGet package?
I don't have a keybaord here with num keys. Can someone please try to repro (do not use the Reactive sample as it's hard coded to a specific old nuget package).
@tig I confirm this still repro only with the ReactiveExample, even updating the NuGet packages.
I think is related with #1132 where some NuGet package might being causing this issue. As it's using the Terminal NuGet package I can't debug it.
I have already managed to debug and actually the symbols [/ * - +.] from the numeric keyboard are not detected, but it may be due the Terminal NuGet package version.
see #977
Possible dupe?
This should be fixed with
- #3078