Equivalent to PGraphics g in p5.js?

[GoToLoop]

@figraham

… when using methods on a _renderer you have to pass arguments as an array and it bypasses all the checks that p5 normally does.

Unfortunately, createCanvas() instantiates a p5.Renderer object, while createGraphics() instantiates a p5.Graphics object, which is a wrapper for a p5.Renderer object, plus it acts as a p5 object too:

Working with mouseDragged() and other mouse events inside a class

Each instance of p5 got a <canvas> element (HTMLCanvasElement) attached to it. Just like a Processing Java Mode’s PApplet got a canvas (PGraphics) as well. When we call createCanvas(), it returns a p5.Renderer object; which is a subclass of p5.Element btW. Besides the main <canvas>, we can create additional offscreen canvases via createGraphics(). However, it returns a hackish wrapper p5.Graphics instead of an actual p5.Renderer! A p5.Graphics got all of the properties of a p5 instance, besides…

It’s very inconsistent & hard to study how the p5js API deals w/ those 2 classes across its source code!

There are other problematic patches to deal w/ p5.Image objects too.
For some reason, the class p5.Image doesn’t inherit from p5.Element!
And therefore, it’s not a parent class for neither p5.Renderer nor p5.Graphics!

BtW, I’ve always ranted & been against this hackish p5.Graphics class from the very beginning of the p5js project.