-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typing some characters in P2D won't return what character was pressed with keyPressed in Processing 4.3 #824
Comments
Created by: bugreporter0 I'm sorry for the weird behavior, I'm new to GitHub and I don't know English very well |
Created by: Hellcat554 I really don’t know what I am doing I’m trying to learn new things I new to On Sun, Feb 25, 2024 at 8:31 PM bugreporter0 @.***>
|
@bugreporter0 What is the key combination you have to press to get the |
I'm bugreporter0. My keyboard has this character as a key, it's a standard AZERTY full size keyboard. The "<" character is next to the left SHIFT key. "<" is not the only missing character, it's just an example. |
The
See https://processing.org/reference/keyPressed_.html You can find the key code for any key by using a tool like https://www.toptal.com/developers/keycode |
The keyCode variable should be set to 60 when I press "<" but println(keyCode) prints "0" in the console when I do, confirming that there really is a problem. Code:
Important: it works in the default render (with keyCode 153 instead of 60 but whatever) but not in P2D. Also, the"Alt Gr" key on my keyboard returns two keyCodes: 17 then 18 when I press it just once. |
Created by: bugreporter0
Description
Expected Behavior
"< was pressed" should be written in the console
Current Behavior
keyPressed detects that a character was typed but not which one when "<" is typed
Steps to Reproduce
Works:
Doesn't work:
Your Environment
Possible Causes / Solutions
Maybe some characters have been forgotten in the keyPressed P2D API in Processing 4 and above because it worked in the last Processing 3 version, I've checked
The text was updated successfully, but these errors were encountered: