On Wednesday, December 19, 2012 10:25:24 Alberto Mardegan wrote: > On 12/18/2012 06:46 PM, Alan Alpert wrote: > [...] > > > C) QGuiAction is added to Gui and is used to create the QML API and > > the bridge with QActions. > > [...] > > > My favorite of those is C), but there is the unresolved question of > > how to make an effective bridge given that we can no longer make > > QAction inherit from QGuiAction. > > I also prefer C (D is also OK). I'm not sure, but I think it might be > possible to make QAction inherit from QGuiAction, as long as the > structure size doesn't change (and I think it won't).
I think my preference is also C. It should be possible for most uses of QAction to use QGuiAction instead, even in widgets, I think. The QWidget* API in QAction is not really central to its functionality. Thanks, -- Stephen Kelly <stephen.ke...@kdab.com> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
