>>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 for the other. > >Agreed for ElementType, could be Element::Type, just 2 characters more to type, outside of Element and > ElementFlag to Element::Flag (although not used as Q_ENUMS(), or should we just ignore those?) >and DynamicRange could be turned into Dynamic::Range. >And Placement to Element::Placement
>(and Accidental::AccidentalType to Accidental::Type, Accidental::AccidentalRole to Accidental::Role, > Dynamic::DynamicType into Dynamic::Type (although not used as Q_ENUMS()), Hairpin::HairpinType > to Hairpin::Type, LayoutBreak::LayoutBreakType to LayoutBreak::Type, Trill::TrillType to Trill::Type, did I miss some?) Working on it see https://github.com/musescore/MuseScore/pull/1005 Bye, Jojo ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
