processing / processing/processing4

with P2D renderer `key` variable doesnt update when pressing CTRL and another key

Open
#795 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug core
Dominant language
Java
Stars
494
Forks
183
Avg merge
4h 39m
Merged PRs (30d)
3

Description

Created by: grimtin10

Description

When using the P2D renderer the key variable doesn't update when pressing control and then another key.

Expected Behavior

Pressing control and then another key should set the key variable to CODED (65535) and then whatever other key you pressed.

Current Behavior

Pressing control and then another key doesn't update the key variable and it ends up containing CODED for both key presses and any subsequent key presses.

Steps to Reproduce

  1. Set renderer to P2D
  2. Create a keyPressed function that prints out the key variable
  3. Press control and then another key

Your Environment

  • Processing version: 4.3 (latest)
  • Operating System and OS version: Windows 10 Pro 22H2

Possible Causes / Solutions

OpenGL renderer isn't updating key variable when it should be.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the P2D renderer using a sketch whose keyPressed function prints key, then compare control followed by another key with subsequent presses. Trace the P2D/OpenGL input handling described in the issue. Done means key reports CODED for control and the correct value for the next key instead of remaining CODED.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
computer-graphics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.