void setup(){
println("arrived at setup");
// force a divide check to illustrate how errors are displayed
int x= 0;
int y= 2/x;
x=y;
}
void setup(){
println(“arrived at setup”);
// force a divide check to illustrate how errors are displayed
int x= 0;
int y= 2/x;
x=y;
}
The code above is a short sample to illustrate. The real code has 1000+ lines and finding where the error happened is quite a chore. I may have to revert to IDE 3.5.3 just to get that help.
I have upgraded from the 3.5.3 IDE to 4.4.4. Run-time errors are not indicating the code line is question making debug a horrendous battle! I am working in Java mode and have reinstalled the IDE, same problem Do I have a setting wrong? Or any suggestions. Thanks
Too many lines to post effectively. I will work up a short example. In the IDE 3.5.3 the editor window to switch to show where the error was detected and highlight that line. 4.4.4 just gives an error message with no clue where it occurred. I will amend my post soon.
Processing 4.0 was a major leap forward from Processing 3.5.4 and certainly had its challenges along the way.
Processing 4.0:
Lots of other changes in between from 4.0 to 4.3.
Processing 4.4 is another step forward from 4.3 and will certainly also have challenges:
Most of the work happened behind the scenes, including various quality-of-life improvements for developers working on the codebase. Key updates include migrating the build system from Ant to Gradle and beginning the transition from Swing to Jetpack Compose Multiplatform . This is part of a global effort to modernize the project’s infrastructure to support future developments, and make it easier for more people to get involved.
“The only constant in life is change.” - Heraclitus
This applies to software as well!
We are all living with this reality and the challenges of updates… it is not just Processing.
It would like to see the issues communicated to users in a simple transparent way.
I don’t have a simple solution for this. The Processing Community Forum and GitHub may not be used by everyone and if they do come here we could direct them to the issues resources as a first step.
A simplified list to current issues could be linked:
On the main Processing website where it is easy to find.
It should be one stop shopping, easy to find and maintained and up to date.
Links to Processing Community Forum and GitHub if further support is needed.
Processing Community Forum may want to have a pinned post linking to it.
GitHub releases could link to it.
I am experienced and that simplifies the process of finding answers and solutions.
Finding help for Processing can be a challenge.
The Processing Community Forum and GitHub are full of useful information, but they also have a lot of different threads, versions, and operating systems to sort through.
It’s easy to get lost or overwhelmed when you’re just trying to find a simple solution.
New and inexperienced users will certainly struggle.
I can also struggle at times!
My preference is always a link to a resource that answer questions; in forum posts that I both read and post. “Teach someone to fish instead of giving them the fish” (short version) empowers users.
All that being said… I would like to see a future update address the reporting of errors sooner than later.
I too find myself using Processing 4.3.4 for bug reporting alongside Processing 4.4.4.
This is an example of one of the issues that could be listed with the Processing 4.4.x current releases.
@ProcessingOrg
Thank you to the Processing team for all the work done in keeping Processing up to date!
Thanks @glv for sharing these links and for your suggestions
Processing is free and open-source, developed and maintained by two people, together with occasional volunteers, and with support from the Processing Foundation. We do our best to share updates as they happen, but we don’t always manage to cover every channel in real time.
As @glv rightly pointed out, Processing is currently undergoing a major technical upgrade behind the scenes and, while we work hard to keep everything functioning as expected, some bugs can slip through.
I know how frustrating it can be when something that used to work no longer does, especially when it slows down debugging your sketches. This particular issue will require bigger changes under the hood before it can be fixed, but we’re on it!
If you’d like to see more about the recent and ongoing work on Processing, these links are a good starting point:
We also welcome contributions from anyone interested in helping improve Processing! If you’d like to work on bug fixes or other improvements, we’re happy to help you get started contributing.
And yes, we have some exciting things in the works that we’ll be sharing soon!
