On 18 December 2012 20:05, Mark <mark...@gmail.com> wrote: > On Tue, Dec 18, 2012 at 6:46 PM, Alan Alpert <4163654...@gmail.com> wrote: >> >> D) QCoreAction is added to Core or Gui and has even less >> functionality, QQuickAction and QAction/QGuiAction build on top of >> that to fill out their API. > > Another option. > > Create a QAbstractAction with the bare minimum that is QML and QWidget > independent. > QQuickAction on top of QAbstractAction to implement the QML specifics. > QAction also on top of QAbstractAction for the QWidget module. Or just > leave the QAction in there as it is since it's "completed" anyway.
How is that different than D? Having a base class would at least give us the chance to reparent QAction to inherit from it in Qt 6; isn't that the only advantage? _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
