FR: TE - Make use of JUCE_DEPRECATED for older functionality

In terms of comms, it’s rather difficult to ascertain what is old and what is new in the Tracktion Engine, and therefore what a user should get started with when outlining a new app structure.

What with the mixture of posts ( Saving and Opening Edits [Tracktion Engine] )

and in-code comments

, it would be much easier to forewarn users by applying JUCE_DEPRECATED, JUCE_CATCH_DEPRECATED_CODE_MISUSE, JUCE_DEPRECATED_ATTRIBUTE, and JUCE_DEPRECATED_WITH_BODY to the TE module where appropriate.

Doing this would be much more intuitive.

1 Like