Thanks for the feedback.
Well now (after hours of try&error to get some plugins running unter MS 3.0) I see some critical functions like newElement() or newScore() are under construction.
Plugins are an important part ,if they are not working I won't consider the released as stable.
But currently Musescore 3.0 is released like that and offered as default download option.
Is that by accident or what's the intention behind this?
... and yes that's the first time I looked into the code.
//---------------------------------------------------------
// newScore
//---------------------------------------------------------
Score* QmlPlugin::newScore(const QString& /name/, const QString& /part/, int /measures/)
{
#if 0 // TODO
if (msc->currentScore())
msc->currentScore()->endCmd();
.... score->startCmd();
return score;
#endif
return 0;
}
Hmm silently commenting out code via the #Precompiler.
What about adding some small 'fence' to the 'construction site' like:
MsgNotImplementedYet( " is currently under Construction", "QmlPlugin::newScore","mscore/qmlplugin.cpp" );
// ^- feel free to elaborate this; that's just an inspiration to get the idea
#if 0 // TODO
...
It won't hurt much, but helps so no one literally stumbles in there without noticing.
Creating scores and elements will probably be disabled a bit longer than editing and tweaking properties. Creating/Removing elements might significantly hurt the layout so we are concentrating on editing scores first.
My understanding is that the plan is to have plugins working about a month after release of 3.0 and that's what I've been telling people. People are content with this, but many people including myself rely on other plugins that are not part of the actual release.
I suggest there be a comment on the download page, at leat in the release notes, that the plugin function is still under construction in the official release of Musescore 3, Or better yet, have a message pop up when someone tries to run a plugin.
If version 2.3.2 is used again and we want to IMPORT and convert a PDF score from this version, it does, but it can not be edited with version 2.3.2; error or file defective.
In version 3.0 I miss the function of the Name Notes plugins; notes that appear below the chosen staff and that you can modify its size, font and horizontal or vertical position. In the new version the name of the notes appear inside the heads of the notes; It's ugly and you do not see it in the scores. Will there be a solution for this function so desired by musicians in learning? Thank you.
Comments
the entire plugin infrastructure isn't really working, 'notenames' is all but one victim
In reply to the entire plugin… by Jojo-Schmitz
Thanks for the feedback.
Well now (after hours of try&error to get some plugins running unter MS 3.0) I see some critical functions like newElement() or newScore() are under construction.
Plugins are an important part ,if they are not working I won't consider the released as stable.
But currently Musescore 3.0 is released like that and offered as default download option.
Is that by accident or what's the intention behind this?
... and yes that's the first time I looked into the code.
//---------------------------------------------------------
// newScore
//---------------------------------------------------------
Score* QmlPlugin::newScore(const QString& /name/, const QString& /part/, int /measures/)
{
#if 0 // TODO
if (msc->currentScore())
msc->currentScore()->endCmd();
.... score->startCmd();
return score;
#endif
return 0;
}
Hmm silently commenting out code via the #Precompiler.
What about adding some small 'fence' to the 'construction site' like:
MsgNotImplementedYet( " is currently under Construction", "QmlPlugin::newScore","mscore/qmlplugin.cpp" );
// ^- feel free to elaborate this; that's just an inspiration to get the idea
#if 0 // TODO
...
It won't hurt much, but helps so no one literally stumbles in there without noticing.
It has been deliberately not finished, but will.
In reply to the entire plugin… by Jojo-Schmitz
Indeed, but this request increases the priority to make this particular plugin work.
In reply to Thanks for the feedback… by djamana_4
Creating scores and elements will probably be disabled a bit longer than editing and tweaking properties. Creating/Removing elements might significantly hurt the layout so we are concentrating on editing scores first.
In reply to Indeed, but this request… by Anatoly-os
My understanding is that the plan is to have plugins working about a month after release of 3.0 and that's what I've been telling people. People are content with this, but many people including myself rely on other plugins that are not part of the actual release.
There is a request about "Chordidentifier" Plugin in the feedback form.
.
In reply to There is a request about … by Anatoly-os
+1 (for chord identifier)
In case there are plugins developers here, please see the following thread for 3.0 plugins API discussion:
https://musescore.org/en/node/282107
The work on plugins support is currently in progress so it is likely to have at least some plugins supported soon.
I suggest there be a comment on the download page, at leat in the release notes, that the plugin function is still under construction in the official release of Musescore 3, Or better yet, have a message pop up when someone tries to run a plugin.
If version 2.3.2 is used again and we want to IMPORT and convert a PDF score from this version, it does, but it can not be edited with version 2.3.2; error or file defective.
In version 3.0 I miss the function of the Name Notes plugins; notes that appear below the chosen staff and that you can modify its size, font and horizontal or vertical position. In the new version the name of the notes appear inside the heads of the notes; It's ugly and you do not see it in the scores. Will there be a solution for this function so desired by musicians in learning? Thank you.
See https://github.com/musescore/MuseScore/pull/4610
fixed in 3ea49316bced899b489788cc88633978e6da3b14
ppitch no more available in MS3 plugins ?
This was useful to handle 8va, but not recognized in my tests.
Harmonica Tablature no longer works in MuseScore 3
It never worked in MuseScore 3. It needs to get adjusted to MuseScore 3.0.2 to run there
Automatically closed -- issue fixed for 2 weeks with no activity.
In reply to ppitch no more available in… by Numerosix
Yes! We need some way of knowing the actual sounded pitch too