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
The Processing size() command takes keywords for each renderer. In addition to the default renderer, other renderers are: (from https://processing.org/reference/size_.html )
P2D (Processing 2D): 2D graphics renderer that makes use of OpenGL-compatible graphics hardware.
P3D (Processing 3D): 3D graphics renderer that makes use of OpenGL-compatible graphics hardware.
FX2D (JavaFX 2D): A 2D renderer that uses JavaFX, which may be faster for some applications, but has some compatibility quirks.
PDF: The PDF renderer draws 2D graphics directly to an Acrobat PDF file.
So, currently the Processing.R example sketch 3d-cube.R:
While this issue is unresolved, I would recommend that current and future example sketches have render keywords defined in the header so that settings() more closely mirrors normal Processing code -- using this style:
Supporting render keywords in Processing.R will make it much easier to translate sketches back and for between Processing(Java) and Processing.R -- especially for new learners.
The text was updated successfully, but these errors were encountered:
The Processing
size()
command takes keywords for each renderer. In addition to the default renderer, other renderers are: (from https://processing.org/reference/size_.html )So, currently the Processing.R example sketch 3d-cube.R:
Would become:
While this issue is unresolved, I would recommend that current and future example sketches have render keywords defined in the header so that
settings()
more closely mirrors normal Processing code -- using this style:Supporting render keywords in Processing.R will make it much easier to translate sketches back and for between Processing(Java) and Processing.R -- especially for new learners.
The text was updated successfully, but these errors were encountered: