Right now, I can only do that on a per-class basis, which creates massive problems when a legacy class gets new scoped enums: I either have to continue with unscoped enums, preventing my users from falling into the Pit of Success, or I have to cut SC and add the magic Q_CLASSINFO.

If I could mark only new scoped enums as scoped-only for QML, I could leave legacy SC as-is and do the Right Thing for new enums.

Since this comes up in every API review round, I think we need this rather urgently, but I'll leave it as P2 for now.

References:

• example of problems when legacy class gets new scoped enums: https://codereview.qt-project.org/c/qt/qtmultimedia/+/651783/comment/679b2fc6_9be4cec2/
• current (insufficient) guideline for Q_CLASSINFO: https://wiki.qt.io/Things_To_Look_Out_For_In_Reviews#Enums Item 6