11-03-2022, 12:21 PM
@Coolman good job!
This is my contribution:
The delay has to be done before calling "_SCREENIMAGE" in particular. Moreover, a delay has to be done just after "SCREEN _NEWIMAGE()" call to give the system time to draw the window, or it doesn't print anything as this program is written.
I wrote this mimicking what I saw in Terry's "QBZERK".
I noticed that before "_MESSAGEBOX" is called there is a delay of at least one second. Maybe it doesn't happen with other users.
This is my contribution:
Code: (Select All)
dim han AS LONG, wd AS INTEGER, ht AS INTEGER
_DELAY 0.5
han = _SCREENIMAGE
wd = FIX(_WIDTH(han) * 0.8)
ht = FIX(_HEIGHT(han) * 0.8)
SCREEN _NEWIMAGE(wd, ht, 32)
_DELAY 1
COLOR _RGB(255, 255, 255)
print "width ="; wd
print "height ="; ht
endThe delay has to be done before calling "_SCREENIMAGE" in particular. Moreover, a delay has to be done just after "SCREEN _NEWIMAGE()" call to give the system time to draw the window, or it doesn't print anything as this program is written.
I wrote this mimicking what I saw in Terry's "QBZERK".
I noticed that before "_MESSAGEBOX" is called there is a delay of at least one second. Maybe it doesn't happen with other users.