# \`juce7\` technical preview branch

**URL:** <https://forum.juce.com/t/juce7-technical-preview-branch/50866>\
**Category:** General JUCE discussion\
**Created:** [April 4, 2022, 1:46pm UTC](https://forum.juce.com/t/juce7-technical-preview-branch/50866 "2022-04-04T13:46:02Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![yfede](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/yfede/32/506_2.png) [@yfede](https://forum.juce.com/u/yfede)\
**Post date:** [April 5, 2022, 8:12am UTC](https://forum.juce.com/t/juce7-technical-preview-branch/50866/27 "2022-04-05T08:12:49Z")

</div>

> [@t0m](#):
>
> See the breaking changes doc for more info about both 1. and 2.: [JUCE/BREAKING-CHANGES.txt at juce7 · juce-framework/JUCE · GitHub](https://github.com/juce-framework/JUCE/blob/juce7/BREAKING-CHANGES.txt)

Now that JUCE\_COREGRAPHICS\_DRAW\_ASYNC is no longer meaningful, I think it would beneficial to give a warning during compilation if it is found to be defined in a project, to give the developer an heads up in case they missed the BREAKING-CHANGES doc.

In general, I think it would be good practise to give such warning for every macro when it is no longer used by JUCE. That would give us developers a chance to clean up our #defines with increased confidence.

(Same idea already mentioned here: [Ouch! kAudioUnitParameterFlag\_IsHighResolution problem, fix needed! - #3 by yfede](https://forum.juce.com/t/ouch-kaudiounitparameterflag-ishighresolution-problem-fix-needed/49425/3))

---

_[View the full topic](https://forum.juce.com/t/juce7-technical-preview-branch/50866)._
