[quote=19620:@William Koperwhats]Luke, I’m willing to give you the benefit of the doubt for now, but even with the following code in the Window.Open event
It still gives a “This file doesn’t exist” error (File: RBXML; Location: “Flicker.Begone”),[/quote]
The exported code didn’t have my API module included, so I gave the raw declares later on. Had Xojo forums allowed users to edit their posts I would of removed the link /code from the Original post to avoid confusion. Just ignore the initial post /download.
[quote]As Joe told, beware of magic declares. ;)[/quote]It’s not even a magic declare, it’s an extended window style that windows added to address flickering issues which was implemented and supported for all windows versions after windows 2000?
You still need to handle all the paint events in WM_Paint for it to work correctly, which xojo may or may not do.
You need to disable Own /Parent device context which is what the first declare does while enabling Savebits, otherwise it’s ignored even if you do successfully set it. There were also some other scenarios where it simply would not work, so something as simple as adding in a certain xojo control could break it.
I’m guessing it’ll still flicker if you have “erase background” set on controls and why erase background is on by default is beyond me.
I’m unaware of whether Xojo’s double buffering option on controls causes any issues.
You can also try enabling or disabling GDI+ to see how that interacts. GDI & GDI+ both I will point out are deprecated and post-windows XP, it switched from GPU to software processes and are slower.
With the above in mind, that’s why it was given “as is” to be tested. Xojo does not make their internals available to users so you can not meaningfully alter core code that affects the entire framework otherwise you might as well just buy the console version of xojo and implement it all yourself. This is simply a minor, intermediate work around.
Some controls may render “oddly” (or to better elaborate, since they now render strictly bottom up) so you have to keep that in mind with layout.