processing / processing/processing4
CTRL+V not posting 22 in P2D/P3D as it does in the default renderer
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
Created by: trackme518
Hi,
normally you can detect CTRL+V as a key==22 (ASCII) inside keyPressed(){} callback. However with P3D renderer this does not work. It also affects other combinations such as CTRL+Z and others.
Minimal code to reproduce the issue:
void setup() {
//size(640, 480 ); //WORKS
size(640, 480, P3D); //DOES NOT WORK
}
int val = 0;
void draw() {
background(val);
val = 0;
}
void keyPressed() {
if (key == 22 ) { //ASCII
println("ctrl+v");
val = 255;
}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal sketch in the issue and compare keyPressed() behavior using the default renderer and P3D, focusing on CTRL+V (key 22) and CTRL+Z. Trace the renderer-specific keyboard input path to determine where the combinations diverge. Done means these combinations are detected consistently in P2D/P3D as they are in the default renderer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100