Is there a way to print a permanent string at a specific location?

[SMcNeill]

@Blpus The reason why your hills aren't working is rather simple:  _PUTIMAGE is glitched and doesn't respect the VIEW SCREEN boundries!

Code: QB64: [Select]

1. $Color:32
2. Screen _NewImage(640, 480, 32)
3.  
4. View Screen(0, 0)-(639, 400)
5.  
6.  
7. Box = _NewImage(40, 40, 32)
8. _Dest Box
9. Cls , -1 'white box
10. _Dest 0 'back to main screen
11. Xchange = 2: Ychange = 2
12. Do
13.     x = x + Xchange
14.     Cls 1, SkyBlue
15.     y = y + Ychange
16.     If x < 0 Or x > 640 Then Xchange = -Xchange
17.     If y < 0 Or y > 480 Then Ychange = -Ychange
18.     _PutImage (x, y), Box
19.     _Limit 60
20.     _Display
21. Loop

My demo above works with CIRCLE and the VIEW SCREEN, but putimage doesn't.  It's a new _UNDERSCORE command, and it's missing the important check for VIEW port limits and needs to be fixed. 

Until it is, you've got to manually bound _putimage coordinates to not allow them to go beyond your VIEW SCREEN limits yourself.  ;)

[bplus]

(Didn't see 2nd post first on page 2) And not rocket science to throw a monkey wrench into that:

Code: QB64: [Select]

1. Screen _NewImage(640, 480, 32)
2.  
3.  
4. View Screen(0, 0)-(639, 460)
5. View Print 30 To 30
6.  
7.  
8. Print "This text stays at the bottom without being overwritten.";
9.  
10. changeX = 2: changeY = 2
11.  
12. Do
13.     Cls 1, -1 'white background for the graphics screen
14.     'moving red ball
15.     x = x + changeX
16.     y = y + changeY
17.     For i = 1 To 25
18.         Circle (x, y), i, &HFFFF0000 'red filled circle
19.     Next
20.     If x < 0 Or x > 640 Then changeX = -changeX
21.     If y < 0 Or y > 480 Then changeY = -changeY
22.     _PutImage , 0, 0, (0, 0)-(_Width - 1, _Height - 16)
23.     _Limit 60
24.     _Display
25. Loop Until _KeyHit
26.  
27.  

Kind of an interesting bug effect...

[SMcNeill]

(Didn't see 2nd post first on page 2) And not rocket science to throw a monkey wrench into that:

Kind of an interesting bug effect...

Aye.  _PutImage currently doesn't respect the VIEW limits, so it can produce some rather oddish results if you don't manually adjust the limits yourself for it.  ;)