Skip to content

[2.0]: code should probably not be reserved by p5 #7799

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

Open
1 of 17 tasks
quinton-ashley opened this issue May 8, 2025 · 0 comments
Open
1 of 17 tasks

[2.0]: code should probably not be reserved by p5 #7799

quinton-ashley opened this issue May 8, 2025 · 0 comments

Comments

@quinton-ashley
Copy link
Contributor

quinton-ashley commented May 8, 2025

Most appropriate sub-area of p5.js?

  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)

p5.js version

2.0.1

Web browser and version

No response

Operating system

No response

Steps to reproduce this

After trying to implement support for p5 v2 in p5play, I found that "Red Remover" still won't launch.

https://game.thegamebox.ca/red_remover/

It declares a function called code

But in p5 v2 there's a prop on p5.prototype called code, though I'm hoping this is a typo and should be keyCode, as it's only declared but never used.

Will workaround by running delete p5.prototype.code.

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

No branches or pull requests

1 participant