(01-31-2026, 07:10 PM)SMcNeill Wrote: You guys are close, but missing the point entirely.
Line 25 is an error as hardware images don't have a destination handle to go to. They go to their own designated screen automagically.
This is the line in question:
Code: (Select All)_PutImage (0, 0), s10, s
This is the correct syntax:
Code: (Select All)_PutImage (0, 0), s10
It's that simple.
Now the problem after it compiles and runs is that hardware images only last a single frame. That END immediately after is going to erase the screen instantly and go to the standard software screen of "Press any key to quit".
Notice how I've trapped that hardware display inside a loop here so you can see it and interact with it, before the program ends:
Code: (Select All)Dim s As Long
Dim s32 As Long
Dim s10 As Long
s = _NewImage(1300, 1000, 32)
Screen s
s32 = _ScreenImage
_Delay .2
_PutImage (0, 0), s32, s
s10 = _CopyImage(s32, 33)
_FreeImage s32
Sleep
Cls , 0
Color , 0
Sleep
_KeyClear
_DisplayOrder _Hardware , _Software
Do
_PutImage (0, 0), s10
Print "INSIDE THE HARDWARE LOOP!"
_Limit 30
_Display
Loop Until _KeyHit > 0
End
The only real change (besides some stuff for the display loop) was just removing that destination parameter on the hardware image.
maybe so, but the question remains did Frederick originally intend on using a hardware image? becuase he does not explicitly state that he was and his code looks like an experiment with images, I wont know for sure until he says one way or the other. I hope he will reply to this and not be another hit and run.
724 855 599 923 575 468 400 206 147 564 878 823 652 556 bxor cross forever


