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.
See https://qt-project.org/doc/qt-5/qtqml-cppintegration-data.html#enumeration-types or https://qt-project.org/doc/qt-5/qtqml-cppintegration-exposecppattributes.html For instance, having brought the ElementType enum outside of the Element class made it unavailable to QML plug-ins. All plug-ins which rely on score scanning to detect element of one type or another (i.e. the great majority of plug-ins) no longer work. This applies to other enum's as well (DynamicRange, Placement, ...). I think something should be done to address this. Thanks, Maurizio -- View this message in context: http://dev-list.musescore.org/Enum-s-and-plug-ins-tp7578860.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
