Hardware images questions

[Dav]

I don't think I fully understand hardware images yet. I know they are different, but not sure how much other than faster loading/displaying.

Once a hardware image is put on the screen, I can't seem to be able to afterwards copy the screen fully with those images on it, like doing a _COPYIMAGE(_DISPLAY) or fading out the screen effect, other screen manipulations,  doesn't seem to work on the hardware images.  It's like they are on a different screen layer or something. Is there a way to manipulate the screen with hardware images on it?

This is another area I need some help understanding about.  Thanks!

- Dav

[Magdha]

I use Hardware images wherever possible and yet have no idea about what they are really: you just have (,33) in the creation code.

So, I shall be very pleased to see the answers of the skilled folks....

[a740g]

There are indeed on their own z-order. Use _DISPLAYORDER to reorder.

If you put it at the back, then you can print stuff over it and also do fades by placing a screen-sized rect with varying alpha.

[Dav]

There are indeed on their own z-order. Use _DISPLAYORDER to reorder.

If you put it at the back, then you can print stuff over it and also do fades by placing a screen-sized rect with varying alpha.

Ah!  _DISPLAYORDER is command I've never noticed before, maybe once when adding that keyword to my IDE, but I didn't learn what it was for.

Thank you!  

- Dav

[a740g]

Also see this from Steve: https://qb64phoenix.com/forum/showthread...3#pid35973

[Pete]

@Dav

_DisplayOrder _Hardware , _Software

That reverses the display order so you can make a hardware background and print software image on top. In SCREEN 0 it allows us to make a hardware background and write text on top. Otherwise, the default is to place a hardware layer or the text layer.

https://qb64phoenix.com/forum/showthread.php?tid=3600

Yes, the copy problem you are experiencing is a layer issue. I recall something similar months ago, but I have appointments out this morning, so I'll have to dig into it more this evening. It involved hardware acceleration in SCREEN 0 and using _copyimage.

Let us know how you are coming along.

Pete