processing/p5.js

new getCamera function for V1 & V2

Open

#8,097 opened on Sep 19, 2025

View on GitHub
 (10 comments) (0 reactions) (1 assignee)JavaScript (3,178 forks)batch import
Area:WebGLFeature RequestGood First IssueHelp Wanted

Repository metrics

Stars
 (20,784 stars)
PR merge metrics
 (Avg merge 9d 8h) (56 merged PRs in 30d)

Description

Increasing access

It would provide compatability between versions 1 & 2 but more importantly provide users and library creators a standard method to access, modify and set cameras.

Most appropriate sub-area of p5.js?

  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)

Feature request details

I suggest a new function for both V1 and V2 that returns a reference to the current camera object, something like

// V2
RendererGL.prototype.getCamera = function(cam) {
    return this.states.setValue('curCamera', cam);
}

// V1
RendererGL.prototype.getCamera = function(cam) {
    return this._curCamera;
}

This would provide compatibility between versions.

Additional comment:

I see that in version 2.0.5 the createCamera method still sets the newly created camera as the default. See issues 5941, 7077 and 7102

Contributor guide

Research direction
Investigate the current camera implementation in both V1 and V2 to design a getCamera function that returns the current camera object. Look at existing getter methods and ensure compatibility.
Tech stack
javascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65