Stupid bicycle vs too large solution.
Posted: Tue Jan 31, 2017 2:28 am
So, now i'm need to repaint some parts of screen every loop pass.
And it's blink.
So, i'm now have only 640kb of ram, and double buffering is too large for it's(because only binary in memory weight approx 300kb).
I'm make for this small bicycle:
Pass counter, when it's > 20k then zero it's and redraw part of screen.
It's fast and reduce blink.
But it's bicycle.
What better? Double buffering in 300kb ram or bicycle with high CPU usage?
And it's blink.
So, i'm now have only 640kb of ram, and double buffering is too large for it's(because only binary in memory weight approx 300kb).
I'm make for this small bicycle:
Pass counter, when it's > 20k then zero it's and redraw part of screen.
It's fast and reduce blink.
But it's bicycle.
What better? Double buffering in 300kb ram or bicycle with high CPU usage?