"TheEndless" wrote:
it just causes a flicker/tear in the screen during the SwapBuffers(), like the draw never completes. Here's a quick sample that causes the issue.
Beautiful short example, it was very easy for me to experiment with it (and of course i observed the buggy behavior too). I found a couple of things more - you dont have even to do
drawRect() - even doing second
clear() shows the issue.
But the fun part is, bug does not happen when roBitmap is
created but when it is
disposed! To verify, just replace assignment
bitmap = CreateObject(...) with appending the new bitmap to an array
arr.push( createObject("roBitmap", ...) ) and... no blinking. So what happens is when you assign the new bitmap to the variable, old one is not used and freed - and there seems to lie the problem. Here is variation of the code that takes bitmap creation outside the loop, to confirm if disposal is the sole suspect:
arr = [] 'prep me 100 bitmaps to drop
for i = 0 to 100:
arr.push( createObject("roBitmap", { Width: 10, Height: 10, AlphaEnable: False }) )
end for
screen = CreateObject("roScreen", True)
While True
screen.Clear(0)
? arr.pop()
screen.Clear(&hFF0000FF)
screen.SwapBuffers()
End While
Run this and watch the console - screen "tears" only until the initial ammo of 100 bitmaps is exhausted and after that is all-red.
Have you flagged someone @Roku on this or should we start jumping up and down waving till someone notices?
This probably should be torn into separate thread...
moderator, please?
