-
Notifications
You must be signed in to change notification settings - Fork 17
Support built-in variables #98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
You mentioned that some variables work -- can you give an example of one that works? In my last round of tests none of them were working, but I might not be calling them correctly. I would say this may be higher than p3 because the majority of all demo Processing sketches use the |
For example: yPos <- 0
draw <- function() {
background(as.integer(204))
yPos <- yPos - 1
if (yPos < 0) {
yPos <- height
}
line(0, yPos, width, yPos)
} I set it to p3 because |
Got it. I see that you've now added width and height, so I'm catching up. I've updated the checklist above for checking off specific things as they are resolved. If it makes sense then break parts of the list off into other issues -- for example, if the interaction constants won't be implemented. Note also the related:
|
For new contributors, it looks like exposing the Currently https://github.com/gaocegege/Processing.R/blob/master/src/rprocessing/RLangPApplet.java#L332 while https://github.com/gaocegege/Processing.R/blob/master/src/rprocessing/RLangPApplet.java#L387 |
Closed since it has been solved. |
OK! -- Is the "keyPressed function vs keyPressed variable" aspect still open via #170? |
Yeah, I haven't solved the issue. |
There are some built-in variables such as height, width and frameCount, some works and others don't work, now.
Screen
Time
Geometry
Interaction
The text was updated successfully, but these errors were encountered: