@mmiscool
Would it be helpful if you put the code higher on the list for real time things so it would find param0 quicker?
Reboot should be dead last one would think... Yet it is the first thing you look for.
A timer should likely be first on the list
next graphical items
etc...
I believe that possibly organizing the code so that it checks for more real time or intense things first might help but I am not a genius here it just seems that ms would matter in this case.
for instance if you put this code somewhere towards the top:
Code: Select allif (Param0 == F("imagebutton"))
{
NewGuiItemAddedSinceLastWait = 1;
numberButtonInUse++;
Param1 = evaluate(Param1);
String tempButton = GenerateIDtag(GOTOimagebutton);
if (Param1.startsWith(F("http://")) | Param1.startsWith(F("HTTP://")) )tempButton.replace(F("/file?file="), "");
tempButton.replace(F("gotonotext"), Param1);
tempButton.replace(F("gotonobranch"), String(JumpList.getPos(Param2)));
HTMLout = String(HTMLout + tempButton);
return;
}
It is one big looped if then statement checking for parameters. Maybe even have cls command towards the top as well IDK but I figure these things will likely save time when I think of it...
Same thing in the eval ino...
Organizing how things are checked should maximize execution at the best possible speed. I remember looking at an emulator of code going through a loop although I didn't know jack about it it was interesting to see the loop it took and how it ran through a buncch of code rather quickly but the less code you must run through the less time it took to arrive and do its thing.
So this is assumption I guess purely so forgive me if this is incorrect in the way that I am thinking.
@tcontrada
here is an html example of a toggle button maybe you could modify the code to fit your needs a bit better.
viewtopic.php?f=40&t=10130forlotto