01-17-2023, 10:51 AM
Just remember guys -- the reason why the 3rd mode is running so fast, is because we're **ONLY** using hardware images with our rendering.
_DISPLAYORDER _HARDWARE <-- see that there's no software screen at all in my display order here.
That means no printing to the screen. No drawing boxes, or circles, or PSETing points. Hardware images are preset images that don't change on us, so they're not the answer to every problem with speed out there.
For @Ikerkaz, it'd probably be a perfect solution for his needs and give him a nice speed boost -- displaying sprites of spaceships zooming back and forth across the screen. For someone who was doing something like a database (like the teacher's gradebook in the other forum's that's been discussed a lot), that's going to require a lot of PRINT statements and user input, and really won't work very well without using a software screen.
For hardware only, you're basically going to be limited to using preset images only -- but if you can write and structure your code in such a manner as to make it work for you, you'll see the performance and speed increases to be a *very* noticeable improvement for your programs. Hardware images aren't the solution for every program out there, but for the ones where they do make sense, *they make a whole lot of sense*!
_DISPLAYORDER _HARDWARE <-- see that there's no software screen at all in my display order here.
That means no printing to the screen. No drawing boxes, or circles, or PSETing points. Hardware images are preset images that don't change on us, so they're not the answer to every problem with speed out there.
For @Ikerkaz, it'd probably be a perfect solution for his needs and give him a nice speed boost -- displaying sprites of spaceships zooming back and forth across the screen. For someone who was doing something like a database (like the teacher's gradebook in the other forum's that's been discussed a lot), that's going to require a lot of PRINT statements and user input, and really won't work very well without using a software screen.
For hardware only, you're basically going to be limited to using preset images only -- but if you can write and structure your code in such a manner as to make it work for you, you'll see the performance and speed increases to be a *very* noticeable improvement for your programs. Hardware images aren't the solution for every program out there, but for the ones where they do make sense, *they make a whole lot of sense*!