News for Musescore 4
I don't know if this is new, but 'ntracks' and 'nstaves' are no longer available in Musescore 4. 'curScore.ntracks' & 'curScore.nStaves' return 'undefined'.
Do you still have an unanswered question? Please log in first to post your question.
Comments
I don't even know what those terms that you refer to are
In reply to I don't even know what those… by underquark
Plugin API related.
In reply to I don't even know what those… by underquark
I'm sorry I'm not understandable, but anyone who frequents this forum should know what I'm talking about. In any case, I'll take this opportunity to make a correction: the properties I was referring to don't only work in the 'on run' function. For you it will be a mystery within a mystery... for others perhaps something interesting. This happens in Linux, I haven't tried in Windows yet.
In reply to I don't even know what those… by underquark
See https://musescore.github.io/MuseScore_PluginAPI_Docs/plugins/html/class…
Well, as soon as I got home, I turned on the PC and then tried to load the plugin again without any changes, and the properties I talked about in this post magically started working again. I have no explanation, but that's how it is. I apologize for the false alarm, forget this post.
Mystery solved: I simply forgot to delete the call to the main plugin window from 'onRun'. Really stupid of me. This fact however raises the question about the opportunity to move to version 4, with some improvements (but not so significant) in the musical notation, and still many problems.