How to disable DirectX in JUCE 8?

[eyalamir]

@reuk

It would be good to know exactly what problems you encountered, so that we can address them individually. Disabling D2D globally is quite a drastic approach, and likely overkill, because it means you won’t benefit from any of the new D2D features - most significantly, performance improvements.

I did report all my issues in a number of relevant threads. See here:

Juce 8 and Direct2D

I believe we’re running into a similar (showstopper) issue as well with horrible performance on Windows since switching to JUCE 8. Switching to the software renderer does not seem to be solving the issues when dealing with ImageFileFormat or other use cases of images created from memory or disk. In general I have to say that it’s an extremely painful breaking change and having a common type like Image be intertwined so heavily with a specific renderer (by default!) seems wrong to me. I think …

The main issue was that performance became horrible and there was no way of disabling D2D to achieve stable builds. It took a couple of days and help from people on the forum to find out all the instances where my performance could be affected.

@reuk

f you want to use a software graphics context to render to an image, you can explicitly pass SoftwareImageType{} when constructing the image

This should be made into an explicit argument that fails builds. Even with hundreds of compile time errors, this would have been easier to fix on my end than the current runtime bug that took a long time to track down.