I think it'd be more likely to happen if the issue #18897: Minim tremolo with beam styling was given a priority, or classified as a bug instead of a suggestion. Given that it's six years old, has had many requests, and is the actual, correct notation for half note minims, which are very common, I don't think either of those things is a radical request.
When a notation program fails at notation, I think it's a bug. Either way, I think it needs a priority assigned if it's ever going to get any work done on it.
Or for me to quit feeling like Theseus in the Labyrinth every time I look at the size of Musescore. I'm going to have to ask a bunch of stupid questions to even be able to build it, let alone find anything in it. Is there an API somewhere?
MuseScore doesn't fail at notating tremolos at all, There are just 2 or even 3 different styles for those and MuseScore so far only supports one.
For building MuseScore there's the developers' handbook
If enough people were to complain about it, Anatoly-os would decide it's time to fix the shortcoming and we'll see him say "dmitrio95 you need to fix this."
I've seen him use the many complaining voices make this a higher priority line.
I'm pretty sure this issue does not deserve a priority high enough (P0) to make it mandatore for the initial 3.0 release, there a many other more pressing issues.
Again: this is not a bug, just a lacking featurea, it lacking since quite long and there is an existing tremolo, which at least serves as a workaround.
But if some volunteer provides a good enough PR, it might happen...
Well, that's my call anyhow, it's subject to change of course. Clearly it's one of the more important new features we could want on the notation side, and of course as we always say, MuseScore is about notation first and foremost. So to me, P0 for initial 3.0 release is about critical bugs and really bad layout, P1 ends up being a bunch of less-critical but still significant bugs and also the most important new features.
Comments
When enough people complain we can't. I don't know how many is enough.
In reply to When enough people complain… by mike320
Not at all a matter of the number of complaints, more a matter of finding someone doing the coding for it. It is OpenSource after all ;-)
See #18897: Minim tremolo with beam styling
In reply to Not at all a matter of the… by Jojo-Schmitz
I think it'd be more likely to happen if the issue #18897: Minim tremolo with beam styling was given a priority, or classified as a bug instead of a suggestion. Given that it's six years old, has had many requests, and is the actual, correct notation for half note minims, which are very common, I don't think either of those things is a radical request.
In reply to I think it'd be more likely… by Laurelin
It is not a bug, just a lacking feaure
In reply to It is not a bug, just a… by Jojo-Schmitz
When a notation program fails at notation, I think it's a bug. Either way, I think it needs a priority assigned if it's ever going to get any work done on it.
Or for me to quit feeling like Theseus in the Labyrinth every time I look at the size of Musescore. I'm going to have to ask a bunch of stupid questions to even be able to build it, let alone find anything in it. Is there an API somewhere?
In reply to When a notation program… by Laurelin
MuseScore doesn't fail at notating tremolos at all, There are just 2 or even 3 different styles for those and MuseScore so far only supports one.
For building MuseScore there's the developers' handbook
In reply to Not at all a matter of the… by Jojo-Schmitz
If enough people were to complain about it, Anatoly-os would decide it's time to fix the shortcoming and we'll see him say "dmitrio95 you need to fix this."
I've seen him use the many complaining voices make this a higher priority line.
In reply to If enough people were to… by mike320
I'm pretty sure this issue does not deserve a priority high enough (P0) to make it mandatore for the initial 3.0 release, there a many other more pressing issues.
Again: this is not a bug, just a lacking featurea, it lacking since quite long and there is an existing tremolo, which at least serves as a workaround.
But if some volunteer provides a good enough PR, it might happen...
In reply to I'm pretty sure this issue… by Jojo-Schmitz
Fwiw, a P3 would have made me thrilled. P1 is a lot higher than I was hoping for.
In reply to Fwiw, a P3 would have made… by Laurelin
Well, that's my call anyhow, it's subject to change of course. Clearly it's one of the more important new features we could want on the notation side, and of course as we always say, MuseScore is about notation first and foremost. So to me, P0 for initial 3.0 release is about critical bugs and really bad layout, P1 ends up being a bunch of less-critical but still significant bugs and also the most important new features.