* The '''QB64''' [[_DISPLAY]] statement can also be used to stop screen flicker without page flipping or [[CLS]] and '''is the recommended practice'''.
* {{Parameter|sourcePage%}} and {{Parameter|destinationPage%}} numbers are limited by the SCREEN mode used. In '''QB64''', the same limits don't apply.
{{Cl|PCOPY}} 100, {{Cl|_DISPLAY (function)|_DISPLAY}} 'function return as destination page
{{Cl|END SUB}} '' ''
{{CodeEnd}}
:''Note:'' Works with [[_DISPLAY (function)]] as the other page. If mouse reads are not crucial, put the _MOUSEINPUT loop inside of the UpdateCursor Sub.
''Example 2:'' Bouncing balls
{{CodeStart}} '' ''
{{Cl|SCREEN (statement)|SCREEN}} 7, 0, 1, 0
{{Cl|DIM}} x(10), y(10), dx(10), dy(10)
{{Cl|FOR...NEXT|FOR}} a = 1 {{Cl|TO}} 10
x(a) = {{Cl|INT}}({{Cl|RND}} * 320) + 1
y(a) = {{Cl|INT}}({{Cl|RND}} * 200) + 1
dx(a) = ({{Cl|RND}} * 2) - 1
dy(a) = ({{Cl|RND}} * 2) - 1
{{Cl|NEXT}}
{{Cl|DO...LOOP|DO}}
{{Cl|PCOPY}} 1, 0 'place image on the visible page 0
{{Cl|CLS}}
{{Cl|_LIMIT}} 100 'regulates speed of balls in QB64
{{Cl|FOR...NEXT|FOR}} a = 1 {{Cl|TO}} 10
{{Cl|CIRCLE}}(x(a), y(a)), 5, 15 'all erasing and drawing is done on page 1
:''Explanation:'' PCOPY reduces the flickering produced by clearing the screen. x(a) = x(a) - 1, etc. is just to be safe that the balls stay within the boundaries. dx(a) = -dx(a), etc. is to keep the actual speed while inverting it (so that the ball "bounces"). The rest should be self-explanatory, but if you are unsure about arrays you might want to look at QB64 Tutorials -> [[Arrays]].