If I remember correctly the previous version used assembler MMX/SSE code to perform graphic operation, and it was fast.
The new code does everything in C++, so it rely on the compiler optimization. This is an issue on debug build, all graphic operations (like bitblt images) take forever.
IIRC, you used to put some pragma magic in the previous version to optimize the code even in debug build, but I can’t find them anymore.
What about adding a #define JUCE_GRAPHIC_OPT 1 in juce config, for us, juce user, that would enable such optimization back, even in debug build ?
I think we don’t need to step into graphic code in our development anyway, so it’s worth it.