"Duplicate method settings()" when using smooth() in setup()

[Gargaj]

Most appropriate sub-area of Processing 4?

Core/Environment/Rendering

Processing version

4.3.1

Operating system

Windows 11

Steps to reproduce this

Creating the following sketch produces the error Duplicate method settings() even though there's only one settings() function; the solution is to remove the smooth() call, which makes the error go away, even though the error message doesn't imply that's the solution.

snippet

void settings()
{
}

void setup()
{
  smooth();
}

Additional context

[plopez01]

Hello and thanks for posting the issue, I have been able to reproduce this. I think it's the same as #823

[Gargaj]

Argh, I searched for "duplicate method settings" on both here and Google :/

[Whiteeth-princess]

thx

[SushantBansal-tech]

@Stefterv and @SableRaf Can you please assign this issue to me .

[SableRaf]

Hi @SushantBansal-tech. Just a quick note: we usually assign one issue at a time per new contributor to help keep things manageable. Thanks for understanding! Once you're done with #898, feel free to comment here again and we’ll be happy to assign this one to you.

[SushantBansal-tech]

@SableRaf Actually I have comment here before this issue #898..

[SableRaf]

Hi @SushantBansal-tech. Not a problem! We're currently focusing on the other issue, so let's keep our attention there for now. Once that's sorted, we can come back to this one :)

[SushantBansal-tech]

@SableRaf I'd like to work on this issue while my previous PR is still in the review process. I'm also interested in submitting a proposal for the project as well . Would that be alright with you?"

[SableRaf]

Hi @SushantBansal-tech, thanks for your enthusiasm!

For new contributors, we usually recommend sticking to one issue at a time to keep things both manageable and fair. Since you’re still working on #898, I’d suggest focusing on that for now. Thanks for your patience while we review it.

Based on your contributions so far, I think this issue might be a bit too complex at this stage, as it requires a deeper understanding of Processing’s core. Once you’ve completed #898 and gained more experience, feel free to check out issues labeled “good first issue” for more opportunities to contribute.

Thanks for your commitment!

[SushantBansal-tech]

@SableRaf So can you please review it #898 as i also want to submit the proposal for GSOC as well and do not have any PRs right now . for the proposal I have also collected some valuable approaches
Here is he PR ; #1020

[SableRaf]

Hi @SushantBansal-tech,

As a reminder, there’s no requirement to have a PR merged for your project to be accepted in GSoC. As mentioned by @ksen0 on the GSoC Discourse thread:

Making lots of PRs might not actually be as helpful to your proposal as taking the time to research and develop a strong technical concept and execution plan.

I really appreciate your enthusiasm and willingness to contribute! Just keep in mind that taking the time to develop a thoughtful proposal and engaging constructively with the community will make a stronger impression than just having an accepted PR.

Showing that you’re mindful of the team’s limited capacity when seeking feedback will also be much appreciated 💙

I recommend attentively reading Kit’s posts on the Discourse thread; they’re highlighted in yellow and contain important guidance for preparing a strong application.

Here’s a relevant section from one of Kit’s messages. I encourage you to read it carefully, as it contains valuable insights:

Selection will be taking the application as a whole. The proposal matters a lot, and a good proposal is one that showcases your idea, and reflects that you’ve done some research (for example, understanding some relevant GitHub issues or commits to find out what specific decisions have been made in the past and why, and what are the concrete challenges of implementing your idea in specific.)

In addition to the proposal, we will consider all forms of contribution, as PF follows the all-contributors spec for both p5.js and Processing 4. The means that you can mention as contribution not only PRs, but also blog posts, events you might have hosted in the past, etc. Contribution also includes constructive participation in our online community spaces - that means GitHub issues as well as here, in this thread! Jumping in and helping to answer newcomers’ questions more quickly than I get to it is 💯 a contribution in the question category!

In the application, the purpose of contribution, like the purpose of research, is to show that you’ve gotten a little familiar with the technologies you’re proposing to work with and that you’re comfortable with the code of conduct and contributor guidelines that applies to the project you’re proposing about.

Both these considerations (technical understanding in the scope of your project and community values and process alignment) are very important, and both are necessary. Neither requires making PRs! You’re welcome to be creative in how you’re approaching showing each of these in the proposal.

[Gargaj]

I looked into it briefly (just by reading the repo) and I suspect it has something to do with https://github.com/processing/processing4/blob/main/java/src/processing/mode/java/preproc/PdeParseTreeListener.java#L372-L380

[SableRaf]

Thanks @Gargaj. I've added your comment to the original issue. I'll be closing this one as duplicate. Let's continue this discussion in #823 💙 Thanks for your sleuthing!