02-25-2023, 07:08 AM
So that's definitely a yes, hardware images will just always behave as if they went to SCREEN,
no matter what DEST is set to. The additional info about DISPLAYORDER makes me wonder... in that case,
why would a preceding DISPLAY stop a following PRINT statement from flickering once, then vanishing,
when it was a part of the hardware image?
Another question - if I only have DISPLAYORDER HARDWARE, will there be a black screen due to some
weirdness like QB64 assuming something about the SOFTWARE side of things? In light of the flicker,
it seems like DISPLAY does have some unusual interaction.
I will run plenty of tests on all this as I have time, there is now a need for me to understand
hardware images as well, and I'll try to answer these questions myself either way, but any extra
light you can shed will likely speed this process up!
no matter what DEST is set to. The additional info about DISPLAYORDER makes me wonder... in that case,
why would a preceding DISPLAY stop a following PRINT statement from flickering once, then vanishing,
when it was a part of the hardware image?
Another question - if I only have DISPLAYORDER HARDWARE, will there be a black screen due to some
weirdness like QB64 assuming something about the SOFTWARE side of things? In light of the flicker,
it seems like DISPLAY does have some unusual interaction.
I will run plenty of tests on all this as I have time, there is now a need for me to understand
hardware images as well, and I'll try to answer these questions myself either way, but any extra
light you can shed will likely speed this process up!