Re: [Mscore-developer] Enum's and plug-ins

2014-06-24 Thread Joachim Schmitz
From: Maurizio M. Gavioli [mailto:miwa...@miwarre.org] There seem to be problems with enum's in the current plug-in framework: according to documentation, to be accessible to QML, enum's should be defined *within* a QObject derived class.

Re: [Mscore-developer] Enum's and plug-ins

2014-06-24 Thread Maurizio M. Gavioli
Jojo-Schmitz wrote From: Joachim Schmitz [mailto: jojo@ ] From: Maurizio M. Gavioli [mailto: miwarre@ ] https://qt-project.org/doc/qt-5/qobject.html#Q_ENUMS: In addition, the class defining the enum has to inherit QObject as well as declare the enum using Q_ENUMS(). Here's where the

Re: [Mscore-developer] Enum's and plug-ins

2014-06-24 Thread Joachim Schmitz
An attempt of simulating an out-of-class enum for QML can be seen at: http://qt-project.org/forums/viewthread/18529 I think it is better to avoid dirty tricks of this kind and pull back those enums into some class; several enums have an obvious class candidate; the Element class could be used

Re: [Mscore-developer] Enum's and plug-ins

2014-06-24 Thread Lasconic
As stated on IRC 1/ I believe the switch from Element::ElementType to ElementType was requested for cosmetic reason only. So there should be no harm in rolling it back. 2/ The typographic simplification is fine and will balance a (very little) bit the previous loss. We just need to make sure we