You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Holding Alt and pressing numbers on keypad allows you to insert special characters..
After version 1.3.0 Holding Alt and pressing numbers ONLY registers the last number pressed..
so instead of getting "~" by pressing Alt+126, I get "♠" which is Alt+6
I'm unable to Insert any symbol who requires 2 or more numbers.
I reverted to 1.2.1 and everything works fine.
The text was updated successfully, but these errors were encountered:
Hi, looking into this issue. I don't have a good understanding of alt codes, so I'd like to gather some more information. Also, I do not have a numpad on my keyboard so I have used AutoHotkey to replicate the keys being pressed, and want to make sure I am testing and handling this right.
Using AutoHotkey, "I" pressed Alt+126 and get "♠". However, when I press Alt+00126, I get "~". I do notice that Alt+6 does get "♠" as well.
Are you sure Alt+126 is suppose to result in "~"? Because I only get that character when I press Alt+00126.
If you can provide the logs.txt and possibly your userSettings.cfg (specifically looking for the json object "keybindSettings") located in %localappdata/RePlays/cfg/, it may assist in debugging this issue.
Yes I'm pretty Sure.
If you actually close RePlays you can see the normal behavour.
I've been using alt commands for a long time and i spent all day trying to figure out what changed on my pc that give me this issue. https://www.alt-codes.net/
Holding Alt and pressing numbers on keypad allows you to insert special characters..
After version 1.3.0 Holding Alt and pressing numbers ONLY registers the last number pressed..
so instead of getting "~" by pressing Alt+126, I get "♠" which is Alt+6
I'm unable to Insert any symbol who requires 2 or more numbers.
I reverted to 1.2.1 and everything works fine.
The text was updated successfully, but these errors were encountered: