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
Hi!
First things first - Thank you very much! For using LepikJS, enjoying the work with it and even for opening the issue.
And I am sorry for later response...
Now, to the actual problem. I am aware of it.
It's wierd but I added this mechanic as a feature because of a simple reason which I came across.
The ASCII value of 0-9 on numeric keys is 48-57.
The ASCII value of 0-9 on numeric keyboard is 96-105. (Also this vary)
Here comes the issue, if it returned an ASCII value instead of number 0-9, the difference between clicking same number on different keys would appear. That is something that (atleast I, as a developer) do not like to manage.
Handling same input on 2 different ASCII values is not ideal.
So here is why it is 0-9 instead of ASCII values.
I would love to hear your opinion on this. Adding why do you prefer ASCII value over numbers would help me understand your problem more.
Also if you want to convert it to ASCII there is built in JS function .charCodeAt(0)
Thanks!
PS: It is not hard to implement this to LepikJS. I hope you got my point, that I do not want to implement something that could potentially cause issues in clicking same number anywhere else on keyboard.
Me again,
I've just discovered that both keyPress and keyRelease events pass integers for keyboard keys 0-9, instead of their ASCII representations.
It's easy to fix in code but would be better if it didn't do that at all.
Again... awesome thing you have created, it opens a world of automation!
The text was updated successfully, but these errors were encountered: