+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1)
+--- Forum: Code and Stuff (https://qb64phoenix.com/forum/forumdisplay.php?fid=3)
+---- Forum: Help Me! (https://qb64phoenix.com/forum/forumdisplay.php?fid=10)
+---- Thread: _Putimage problem. (/showthread.php?tid=3591)
Pages:
1
2
RE: _Putimage problem. - TempodiBasic - 04-08-2025
Quote:It's just not possible. Software images are for manipulation. Hardware images are *just* for display. Once they're created, that's it.I had learnt this concept when I understood that Hardware and GLrender are other layers that can be displayed on/together software layer but are indipendent among them and software section. Graphic instructions work on software layer, OpenGl instructions work on GLrender layer, no instruction works on hardware layer.
So Img3 = _copyimage(t,33) copies the software layer on Img3... and there is nothing at that layer, so nothing has been copied in Img3.
Layer Instructions/Keywords Default
Software layer <-- graphic instructions showed
Hardware layer <-- no instructions hidden
GLrender <----- OpenGl instructions hidden
if you put END at the place of SYSTEM at line 25 of your example you see that hardware images disappear because there is no further refreshing of aspect of window's application. You see all together but that is a stack of layers no one layer.
RE: _Putimage problem. - Pete - 04-08-2025
And that , my friend, is why we need to be cpu conscious when using hardware acceleration.
When debugging, I just use _DISPLAY: SLEEP. That will update all the hardware and software images and keep the hardware ones from disappearing.
Pete