01-15-2023, 12:27 PM
(01-15-2023, 10:09 AM)Fantomas Wrote: Hi,
Thanks for your replies !
But as i use "_fullscreen", i don't need "_Screenmove _Middle" !
But as i said, it's works fine before with v3.4.1
Regards
It does. You're 100% correct with that. What's changed was:
Quote:#66, #270 - GLUT commands are now always executed on the correct thread. This fixes issues where some programs would randomly crash.
_SCREENMOVE _MIDDLE used to need a delay before it was executed properly at program start up. It's one of those commands which got moved into our glut queue, so as to not have any problems with execution or crashing, as it had before. Several other glut commands got moved into the new glur queue as well, such as _DesktopWidth and _DesktopHeight, and several other things.
_FullScreen, on the other hand, simply got missed and remained in the original thread, without going into the glut queue that we just created in v 3.5. This led to it being in a race condition for when it was executed in its thread, vs when a glut command -- such as _ScreenMove -- was executed off its queue. In the case which you've noticed and shared, _Fullscreen is a click faster than _ScreenMove, so your program flashes into fullscreen mode and then gets knocked out of it when it's moved and repositioned with _ScreenMove.
The glitch is 100% something which we created with the changes in 3.5, but the good news is that this is a very simple fix. _FullScreen just needs to go into the glut queue and get processed in the proper order there, without the race condition of it being in the wrong thread.
This problem will go away for good, once we release the next update to PE in a couple of weeks. Until then, you can get by with either adding a delay to prevent the race condition, or else get rid of the _ScreenMove itself.
If anyone spots any of the other screen commands which act or behave strangely, kindly let us know. We're just human, and we can easily overlook things that are interconnected like this, when testing changes and bugfixes. It's only with all your guy's help -- our lovely user base -- that we find these little oversights and fix them.
Keep up the good work, guys!
