Thanks for watching and taking the time to comment. I am not sure I understand your question. I do use the variables to count up. If you are asking about using a smaller time base of 500 milliseconds then you are correct. If all of your timing is in seconds then you could use a 1 second timer. If you you have one delay of 3 seconds but another delay of 1.5 seconds then you need to adjust the timer to your needs. In some programs I have written I need to set the timer to 50 milliseconds so I can get all the timing correct. I apologize if this does not answer your question. Please, feel free to rephrase your question if I did not answer correctly. You can also go to www.cheapcontrols.com and submit your question. I will reply through email and we can have a more in depth conversation.
@@CheapControls Thanks for the reply and sorry for the confusion. I was a little confused because you used three variables to get a 3 second delay. But your explanation made it clear to me too. I was just worried that it would be necessary to set a particularly small time (50ms) for the timer to avoid any problems with the Nextion display. But if you use the example in other programs where a higher resolution is required, then it's clear. Thank you.
Great idea about how to simulate delays with a timer. About the animations, I know that you can do a simple animation by switching many images one by one, but this uses a lot of free memory on the Nextion display and unfortunately some of them don't have much, is there a better way? also I would love to see how to make some cool UI elements like rotary dials (you can probably use AI to to the graphics for you).
The first video will be the mutli-image way with all the displays and then a better way with the intelligent displays. I am going to try to come up with a better way for lower end displays in a follow up video.
It's great to see you back on. Thanks for your work.
Your Welcome, It is good to be back.
At first: great series of tutorials. I really appreciate it. One question: why don't set the time to e.g. 1sec and use the variable to count up to 3?
Thanks for watching and taking the time to comment. I am not sure I understand your question. I do use the variables to count up. If you are asking about using a smaller time base of 500 milliseconds then you are correct. If all of your timing is in seconds then you could use a 1 second timer. If you you have one delay of 3 seconds but another delay of 1.5 seconds then you need to adjust the timer to your needs. In some programs I have written I need to set the timer to 50 milliseconds so I can get all the timing correct. I apologize if this does not answer your question. Please, feel free to rephrase your question if I did not answer correctly. You can also go to www.cheapcontrols.com and submit your question. I will reply through email and we can have a more in depth conversation.
@@CheapControls Thanks for the reply and sorry for the confusion. I was a little confused because you used three variables to get a 3 second delay. But your explanation made it clear to me too. I was just worried that it would be necessary to set a particularly small time (50ms) for the timer to avoid any problems with the Nextion display. But if you use the example in other programs where a higher resolution is required, then it's clear. Thank you.
Glad I was able to clarify.
Great idea about how to simulate delays with a timer. About the animations, I know that you can do a simple animation by switching many images one by one, but this uses a lot of free memory on the Nextion display and unfortunately some of them don't have much, is there a better way? also I would love to see how to make some cool UI elements like rotary dials (you can probably use AI to to the graphics for you).
The first video will be the mutli-image way with all the displays and then a better way with the intelligent displays. I am going to try to come up with a better way for lower end displays in a follow up video.