Quote:
Originally Posted by Geoff Waddington
Yeah, that's why, in the end, decided against using JUCE on the CSI project, one too many moving targets
|
I honestly don't understand how you came to that conclusion. My JUCE based projects that don't rely on an altered JUCE code base have had very few problems using the latest latest JUCE versions from the develop branch from their git repo. I do a git pull on the JUCE develop branch almost every day and it happens only a few times a year I actually have to change/fix something in my own code because of that or I need to report a bug in their forum. Things would be even more stable if one doesn't live on the edge and just uses their master branch which they don't update that often.
The project that is the topic of this thread is obviously an exception. It simply does things that are not supported by JUCE and relies on keeping an internally modified JUCE version in sync. (Which is a very non-ideal situation.)