_DISPLAYORDER Question

[TerryRitchie]

Terry Ritchie, Examples 1 and 2 works well. None of SMcNeil's Marvin Martian in them.

Thank you for checking the programs out.

@SMcNeill Yeah I remember those days too. I never did understand the hate for having to include a few .DLL files along with the .EXE. I simply used Innosetup to compile a nice clean installer for the software I distributed. Hell, Innosetup even set up an uninstaller in the start menu for you as well. And best of all it was free.

I wish Galleon would have just continued to update on his own timeline and ignored all the requests/negativity/etc.. I often wonder if he has been working on his vision of what QB64 should be and will release it to the world some day.

Ok, so _HARDWARE1 is not implemented then. I'll be sure to include in the tutorial that even though the keyword is accepted it's a feature that's planned for the future. Having 2 (or more) hardware surfaces to work with would really be handy.

One other thing I noticed by accident. I was under the assumption that hardware images would not even display if the _DISPLAY statement was not used. Turns out they will but for a very, very brief time. You need to keep the image drawing in a very tight fast loop for it to do any good though. I'm going to instruct tutorial users that best practice is to use _DISPLAY with hardware images.