Plugins in development branch: Unable to handle unregistered datatype 'Score*'
Hi,
I've compiled musescore from a fresh git checkout, under linux (crunchbang, based on debian wheezy).
I'd like to get into making musescore plugins, but cannot get any to run. For example here is the output from the stock "walk" plugin, with the default score loaded (bilder einer ausstellung):
cannot read synthesizer settings
ChordList::read
parse: source = , handle = <>
parse: HChord = (145)
parse: xmlKind = , text = <>
parse: xmlSymbols = no, xmlParens = no
parse: xmlDegrees = <>
cannot load qml translations
Hello Walker
QMetaProperty::read: Unable to handle unregistered datatype 'Score*' for property 'Ms::QmlPlugin::curScore'
QMetaProperty::read: Unable to handle unregistered datatype 'Score*' for property 'Ms::QmlPlugin::curScore'
QMetaProperty::read: Unable to handle unregistered datatype 'Score*' for property 'Ms::QmlPlugin::curScore'
file:///usr/local/share/mscore-2.0/plugins/walk.qml:27: TypeError: Result of expression 'curScore' [undefined] is not an object.
Does anyone have tips for how to get this working? I wanted to use the development checkout version because I also need OSC control.
Best wishes,
alex
Comments
as this concerns the development version , this should rather be discussed in the technology preview forum ;-)
There was a possible related and meanwhile fixed issue: #17062: Problem with curScore in plugin.
And another one: #20907: Plugins crash if no score is open
But I can confirm your problem, using e1bb948
Warning: QMetaProperty::read: Unable to handle unregistered datatype 'Score*' for property 'Ms::QmlPlugin::curScore'
Warning: QMetaProperty::read: Unable to handle unregistered datatype 'Score*' for property 'Ms::QmlPlugin::curScore'
28:-1: TypeError: Result of expression 'curScore' [undefined] is not an object.
In reply to as this concerns the by Jojo-Schmitz
Hi, thanks for confirming, and apologies for posting in the wrong place.
This seems a far-reaching problem to me, shall I open an entry in the issue tracker?
In reply to Hi, thanks for confirming, by yaxu
Yes, I think this should be done