I just installed R2016R4 on a Windows 10 machine and to my surprise I immediately experienced a multitude of issues. I can’t believe that Xojo released this version for the Windows platform.
Many things that are supposed to have transparency are now opaque, even in the GUI of Xojo itself. However, the biggest problem for me is that none of the soft declared GDIPlus API procedures are working anymore. And I use these a lot, such GdipDrawLinesI to draw dotted and dashed lines, as well as for other graphics artifacts that are unavailable or do not work well in Xojo.
So it’s back to 2016.R3. I Assume that the GDIPlus API call problem is caused by the introduction of Direct2D. Question is: Is this going to be solved?
Wow. That’s a little unexpected to have something being depreciated for which there is not really an alternative. I will see if I can render the GDI content to the Direct2D render target. Does look rather complicated.
I will inspect the other issues I encountered and report feedback cases. I did read the release
UseGDIPlus is deprecated in the sense that you can still build code that references the property without a compilation error. But the Windows graphics framework is now entirely built around the more modern Direct2D- so there really isn’t much sense in setting an old property that doesn’t mean anything to the modern graphics in 2016r4+. Any GDI/GDI+ specific declares of course, may have to be updated, since the framework itself no longer uses GDI/GDI+.
Like macOS, we now use modern drawing at all times and users don’t have to think about when GDI+ should be used vs GDI anymore.