Skip to content
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

feature: don't erase canvas during recompile #19

Closed
osresearch opened this issue Jul 26, 2019 · 1 comment
Closed

feature: don't erase canvas during recompile #19

osresearch opened this issue Jul 26, 2019 · 1 comment

Comments

@osresearch
Copy link

osresearch commented Jul 26, 2019

It would be nice for some performance to not have the canvas erased during a recompile. This might require hacking on the underlying p5 code to preserve the canvas if it exists.

@ffd8
Copy link
Owner

ffd8 commented Jul 26, 2019

Right now I'm developing a 'soft recompile', so that if you only make changes to the draw() function, it will simply inject those changes into the draw() of the iFrame, avoiding that momentary flash of a background..! I ran into the issue of that flash at the last VJ event I did. Any other changes, to setup/global etc– would require a complete recompile to get those variables etc. No major hacking of p5 necessary.. luckily figured out how to do it by appending to the iFrame. Update coming soon as I do further tests and make sure it's working for COCODING mode.

Here's a demo (as I just started developing this feature a couple days ago):
https://www.instagram.com/p/B0UCtnrCw_Z/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants