Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
_Putimage problem.
#11
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.
Reply
#12
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
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  I'm looking for suggestions to solve the problem! Petr 10 649 02-05-2026, 04:56 PM
Last Post: ahenry3068
  Nth problem with hardware images Ikerkaz 9 471 01-23-2026, 02:58 PM
Last Post: bplus
  _Putimage Question. Pete 11 672 01-04-2026, 09:33 PM
Last Post: Pete
  Install problem...... jssantoro 6 380 12-17-2025, 08:31 PM
Last Post: madscijr
  _putimage (Solved) Pete 0 217 11-16-2025, 06:48 AM
Last Post: Pete

Forum Jump:


Users browsing this thread: 1 Guest(s)