Skip to content

p5.js mode not working in 4.4.1 #1055

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

Closed
Stefterv opened this issue Apr 20, 2025 · 3 comments · Fixed by #1056
Closed

p5.js mode not working in 4.4.1 #1055

Stefterv opened this issue Apr 20, 2025 · 3 comments · Fixed by #1056
Labels
bug Something isn't working
Milestone

Comments

@Stefterv
Copy link
Collaborator

Most appropriate sub-area of Processing 4?

PDE

Processing version

4.4.1

Operating system

All

Steps to reproduce this

Install p5.js mode
2.
Select p5.js mode in the editor
3.

snippet

No response

Additional context

No response

Would you like to work on the issue?

already fixing

@Stefterv Stefterv added the bug Something isn't working label Apr 20, 2025
@Stefterv Stefterv added this to the 4.4.3 milestone Apr 22, 2025
@marioguzzzman
Copy link
Contributor

Hi, I wanted to add a quick note since I just encountered this too.

The issue still exists when using the official Processing app (downloaded from the website).

But, when I built Processing myself from source using IntelliJ (following the steps in BUILD.md), everything worked and the Mode works properly.

So it seems like the bug might only affect the prebuilt version, not the code itself. Maybe something in the packaging/distribution?

I'm on Windows 11 (amd64) using IntelliJ IDEA 2024.3.4.1 Community Edition.

cc @Stefterv since you originally fixed this, just wanted to mention in case this detail helps. Let me know if it makes sense to open a follow-up issue or test anything further.

@SableRaf
Copy link
Collaborator

Hi @marioguzzzman and thanks for the update! Just to clarify: are you using version 4.4.1 from the website? The bug is still present in that release. It was fixed in the current beta (4.4.3), which includes the missing module. The issue shouldn't appear there.

Let us know if it still happens in 4.4.3 so we can investigate further.

@marioguzzzman
Copy link
Contributor

@SableRaf It took me a couple of days to test, but you are right, the beta version 4.4.3 does not present that issue. Thank you for the clarification and thanks @Stefterv for fixing the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants