[v4.0.2 and above] “Cannot find a class or type named ‘PApplet’” error

[processing-bot]

Created by: 12people

Description

I’m maintaining an open-source Processing app called FOSStriangulator . It used to compile just fine with every Processing version I’ve tried up until Processing 4.0.2. Now, with Processing 4.0.2 and newer versions, it won’t compile, whereas with 4.0.1, it still does. With the newer versions, it’s giving me this error:

Cannot find a class or type named “PApplet”

It’s also giving me a range of errors, all seemingly random, such as not being able to find classes like PImage, PrintWriter, IntList, etc.

I looked at the 4.0.2 release notes 1 and I can’t see any change that might be causing the issues.

I originally posted about this on the forum and I was directed to file a bug report here.

Expected Behavior

I was expecting the app to run without a problem, just like it does on all the Processing versions I tried before 4.0.2.

Current Behavior

As described above, running the app on versions 4.0.2 and above gives the Cannot find a class or type named “PApplet” error and fails to run.

Steps to Reproduce

1. Clone the FOSStriangulator repository.
2. Open the project up in Processing 4.0.2 or above.
3. Run the project.

Your Environment

• Processing version: 4.0.2 and above (I tried every major version)
• Operating System and OS version: macOS 13.1 on ARM; also independently verified on Linux

[processing-bot]

Created by: benfry

@sampottinger Possible preproc changes in 4.0.2 causing this?

[processing-bot]

Created by: sampottinger

I'll take a look @benfry!

[processing-bot]

Created by: sampottinger

Hey all! Sorry for the issue here @12people.

@benfry I was trying to beautify the output Java file and part of that was trying to detect if the user was importing processing.core on their own, preventing duplicate imports from being written by the preproc. So, users who manually import processing.core.* wont see preproc generated import statements for processing.core objects.

This code imports part of processing core explicitly (https://github.com/FOSStriangulator/FOSStriangulator/blob/37fb816cc70dc4315c8a26b0b0db1411b20ffb20/FOSStriangulator/DTEdge.pde#L30) but not all of it. My change (#597) was problematic if the developer uses a package from default imports under processing.core without explicitly importing it but explicitly importing something else from processing.core as the preproc wont try to write the default imports for them to prevent duplication. Thinking more on this, unless you are opposed, I would recommend just allowing the duplicated imports to be written by the preproc in this instance. Though it may lead to duplicitous code, it is most consistent with historic behavior.

This fix is implemented with #635. My apologies to both of you for the bug. @12people I have tested FOSStriangulator with my code fix and it builds successfully.

[processing-bot]

Created by: benfry

Great, thanks for taking a look Sam. It happens!

Merging in the fix for 4.1.2.

[processing-bot]

Created by: 12people

Amazing, thanks a ton!

[processing-bot]

Created by: github-actions[bot]

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.