From e786f9c0aa94cd67376d6863a5cfac1ca6d818c9 Mon Sep 17 00:00:00 2001 From: Tom Poole Date: Fri, 16 Nov 2018 10:28:06 +0000 Subject: [PATCH] Clarified some text in the breaking changes doc --- BREAKING-CHANGES.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/BREAKING-CHANGES.txt b/BREAKING-CHANGES.txt index 94086eefb0..76eb6e15a6 100644 --- a/BREAKING-CHANGES.txt +++ b/BREAKING-CHANGES.txt @@ -41,8 +41,7 @@ Possible Issues which is no longer part of JUCE. 2. Building a VST2-compatible VST3 plug-in (the previous default behaviour in JUCE) requires header files from the VST2 SDK, which is no longer part of - JUCE. When a new JUCE plug-in project is created the option - JUCE_VST3_CAN_REPLACE_VST2 will be set to zero. + JUCE. Workaround ---------- @@ -54,6 +53,8 @@ Workaround version, and you want the VST3 plug-in to replace the VST2 plug-in in hosts that support it, then you should enable the JUCE_VST3_CAN_REPLACE_VST2 option. +3. When a new JUCE plug-in project is created the value of + JUCE_VST3_CAN_REPLACE_VST2 will be set to zero. Rationale ---------