which is a somehow "main and basic"-tutorial. I don't want to post additional explanations to the blink-without-delay-tutorial in a forum. I'm convinced that I'm able to write a real improvement to make things easier to understand and to expand on additional and more detailed examples. Of course some administrative checking if it is really an improvment should be done. Where should I write to to supply my suggestions directly to the person who can decide "yes that's worth it" or "no it's not worth" ?
You can submit your suggestions to Arduino support:
That certainly won't achieve your goal of communicating directly with the person who will make the decision. That's simply not the way things work at Arduino. When you contact support, it creates a ticket, which the support staff vet and triage. Only after that process will they transfer the ticket to the people in charge of maintaining the tutorial content.
Although it sounds like you're already set against it, you are welcome to post your ideas here first to get feedback from the community. After all, the Arduino users here on the forum and the very audience for the tutorial.
OK so which sub-forum do you suggest for an improved version of how to use millis() as a non-blocking way to execute parts of code "delayed" ?
best regards
StefanL38:
OK so which sub-forum do you suggest for an improved version of how to use millis() as a non-blocking way to execute parts of code "delayed" ?
Also, I suggest that you try to keep your version of the Tutorial to about the same length as the existing one. Long explanations are generally not useful for beginners.
IMHO the existing Tutorial is fine but everything can be improved. I would like to see your suggested text.
your tutorial several things at a time uses servo.h.
This means to really complete the execise in reality the user needs a servo.
IMHO tutorials that show coding-techniques (=software) should always be reduced to the minimal hardware-requirements ever possible. Of course if the tutorial is about some additional hardware f.e. a temperature-sensor the temperature-sensor is required. But leave out the LCD, the buttons, the LEDs (except the onboard-LED) and do everything with the COM-Port which must be there anyway.
recently I came across a posting where a newbee was using millis() in the wrong way. He was not aware of the fact that the loop will run through thousands of times until the elapsed-time-condition becomes true. So an example that shows this on the serial monitor IMHO would be a good extension to the millis()-beginners guide.
My initial question was evoked through the blink without delay "tutorial"
my suggestion is delete this short democode or extend the comments to make it easy to understand for newbees or add a link inside the demo-code and on the website to guide newbees to the beginners-guide.
StefanL38:
my suggestion is delete this short democode or extend the comments to make it easy to understand for newbees or add a link inside the demo-code and on the website to guide newbees to the beginners-guide.
Start a Thread (with a suitable Title) in the Programming section and in it post the text and code that you think would be appropriate.