You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, happened to me a couple of times with noSmooth() or smooth(). That must go into settings() .
But, on the other hand, settings() are very restrictive, you cannot have eg. frameRate(), background(), stroke(), fill(), noCursor(), surface.setVisible() etc. in there - you'll get NullPointerException.
changed the title [-]having noSmooth(); in steup will trigger a duplicate settings() warning[/-][+]having noSmooth(); in setup will trigger a duplicate settings() warning[/+]on Nov 28, 2024
Thanks very much to @nightshining, @wacala, and everyone who reported this issue 💙
This is confirmed to be a bug, and we’re currently investigating. At this point, additional reports aren’t needed, but feel free to add a 👍 on the original post if you’re also encountering this issue. We’ll keep this thread updated as things progress.
Note
If you’re curious about the cause of this bug or want to help with a fix, the Processing code is open source and contributions are always welcome! Check out our contribution guidelines for instructions. We're also here to offer guidance to new contributors so if you need help getting started, feel free to ask.
Activity
processing-bot commentedon Mar 8, 2024
Created by: JuzerNejm10
Yeah, happened to me a couple of times with noSmooth() or smooth(). That must go into settings() .
But, on the other hand, settings() are very restrictive, you cannot have eg. frameRate(), background(), stroke(), fill(), noCursor(), surface.setVisible() etc. in there - you'll get NullPointerException.
Stefterv commentedon Nov 16, 2024
Seeing the same thing @clankill3r, I will look into it
benfry/processing4#823
[-]having noSmooth(); in steup will trigger a duplicate settings() warning[/-][+]having noSmooth(); in setup will trigger a duplicate settings() warning[/+]nightshining commentedon Mar 12, 2025
Same issue. Mac 4.3.3 Need to use fullscreen() in settings()
Duplicate method settings() in type
wacala commentedon Mar 27, 2025
Same here. Processing 4.3.4 for Mac, M1 processor, macOS Sequuoia.
SableRaf commentedon Mar 27, 2025
Thanks very much to @nightshining, @wacala, and everyone who reported this issue 💙
This is confirmed to be a bug, and we’re currently investigating. At this point, additional reports aren’t needed, but feel free to add a 👍 on the original post if you’re also encountering this issue. We’ll keep this thread updated as things progress.
Note
If you’re curious about the cause of this bug or want to help with a fix, the Processing code is open source and contributions are always welcome! Check out our contribution guidelines for instructions. We're also here to offer guidance to new contributors so if you need help getting started, feel free to ask.
SableRaf commentedon Apr 1, 2025
@Gargaj said in #861 (comment)