Senior Member
Joined: 25/05/2023
Location: GermanyPosts: 204
| Posted: 06:09am 13 May 2026 |
@ LeoNicolas:
many many thanks for your energy to help me.
you wrote:
"Scanning Out of Sync: The display hardware refreshes the screen many times per second (usually 60Hz). It reads the memory line-by-line. If your MMBasic code is halfway through drawing a large circle while the hardware is scanning that same area, the monitor will display half of the old frame and half of the new one. This causes artifacts, specially with moving objects, and flickering
Slow Execution: MMBasic is an interpreted language. While fast, it isn't fast enough to update thousands of pixels in the tiny window of time between screen refreshes."
yes and ok. in this situation i comprehend mistakes of reading and showing screen memory content; i do not understand (until now) that there remain "wrong bytes" in the screen memory because the systems routine that "give" the data to the vga output only reads (from screen memory) so the screen memory content must be (or stay) correct after a while. but i will think further and again.
your solution in my program does not flicker. so i will go this way and test.
again: many many thanks.
until now i do not read your text completely but i hope to have time during the next week end.