Cool, we are on the same page here, because that's just what I was looking into when you made this post. Certainly the usage will be more with hardware acceleration in SCREEN 0 than just utilizing pure graphics, but as long as it isn't alarmingly elevated, it still may be worth pursuing.
I'll have a look at your code and update my demo accordingly. I'll let you guys know the improvement when the results are in...
Edit...
NEAT! Dramatic improvement from 55% to 35% just by making it so the overlay image copy is only made once and freed once per sub loop.
So the difference in testing the original, do you think it's the difference in our hardware? The desktop you are using is infinitely more powerful than this 12 year old laptop I'm coding on.
Edit #2:
I ran with your idea on the graphic/hybrid buttons. I had to tweak the code a bit more and a bit differently, but yep, you were correct, it also helped reduce CPU, now down to 23%.
You know I did try the system idle approach a few days ago, but it wouldn't display the non-text items. I think I didn't revert to _autodisplay. I'm going to retry that, next...
Pete
I'll have a look at your code and update my demo accordingly. I'll let you guys know the improvement when the results are in...
Edit...
NEAT! Dramatic improvement from 55% to 35% just by making it so the overlay image copy is only made once and freed once per sub loop.
So the difference in testing the original, do you think it's the difference in our hardware? The desktop you are using is infinitely more powerful than this 12 year old laptop I'm coding on.
Edit #2:
I ran with your idea on the graphic/hybrid buttons. I had to tweak the code a bit more and a bit differently, but yep, you were correct, it also helped reduce CPU, now down to 23%.
You know I did try the system idle approach a few days ago, but it wouldn't display the non-text items. I think I didn't revert to _autodisplay. I'm going to retry that, next...
Pete