2 posts • Page 1 of 1
This is a bug. Thank you for pointing it out. We had assumed that the library we are using to handle input automatically responded to the num-lock state but it seems like it's not the case. I don't think there is a way to work around it so you will need to wait for an update.