Thinking about it, yeah, I agree. If I make the code faster, it'll probably just look worse. Though for my own edification, what would be the best optimization strategy here?
render into an off-screen buffer during "wait" cycles. Then print the entire buffer when my interval elapses in scrollString()
The only other strategy I know of is "the long way", instrument each function to track and print an average execution speed. Then rework each function starting with the slowest one. I'm a Linux guy, where strace
will do function-timing for you.
Are there any handy debugging libraries or similar tools for Arduino which can do this?