On Thursday, 16 July 2020 04:04:58 PDT Volker Hilsheimer wrote: > But we don’t have to be "all or nothing” on any class; old and new > properties can be mixed. Some of the more complicated properties won’t fit > into the QProperty design, and they can stay as they are, just not > supporting binding. That’s fine, QAction::iconVisibleInMenu for example is > maybe not the kind of property that requires bindings.
I'd rather we comply with our own, future guidelines as much as possible. If a property is meant to be bindable in a new class, it should be bindable in an existing class in Qt 6.0. Modulo wholesale module exceptions like QtWidgets. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
