You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Am getting the following friendly error message from p5 concerning arguments passed to the p.image() (with p5 in instance mode).
p5.js says: image() was expecting p5.Image|p5.Element for parameter #0 (zero-based index), received p5.Element instead at webpack-internal:///239:103:9. [http://p5js.org/reference/#p5/image]
Message results from calls such as this: p.image(video, p.mouseX-vWidth/2, p.mouseY-vHeight/2, vWidth, vHeight);. Video in this case is a p5.MediaElement returned from p.createCapture( p.VIDEO ).
It is unclear as to what is required to resolve the issue since the friendly error message says it was 'expecting a p5.Image or p5.Element' and has 'received p5.Element instead' (p5.MediaElement apparently being a subclass of p5.Element).
(NB: Was referred here from the Processing forum)
The text was updated successfully, but these errors were encountered:
Found a bug
Existing feature enhancement
New feature request
Image
Desktop/Laptop
p5.js version: 0.6.0
Steps to reproduce this:
Am getting the following friendly error message from p5 concerning arguments passed to the p.image() (with p5 in instance mode).
p5.js says: image() was expecting p5.Image|p5.Element for parameter #0 (zero-based index), received p5.Element instead at webpack-internal:///239:103:9. [http://p5js.org/reference/#p5/image]
Message results from calls such as this:
p.image(video, p.mouseX-vWidth/2, p.mouseY-vHeight/2, vWidth, vHeight);
.Video in this case is a
p5.MediaElement
returned fromp.createCapture( p.VIDEO )
.It is unclear as to what is required to resolve the issue since the friendly error message says it was 'expecting a p5.Image or p5.Element' and has 'received p5.Element instead' (p5.MediaElement apparently being a subclass of p5.Element).
(NB: Was referred here from the Processing forum)
The text was updated successfully, but these errors were encountered: