This is actually a duplicate of a fixed bug https://musescore.org/en/node/177586 Slurs disappear, in the most cases, after editing and Escape if the bordering note values are different
How do you make the issue with the name one like you did, rather than copy and paste the URL then the title like I did? It will be less confusing if I can do that and it will be less likely to have duplicates (such as this).
On that note, if/when the issue tracker is retired and we use GitHub, I hope you can do some special coding for the new MuseScore.org to similarly display GitHub issue links according to their current title and status.
@Isaac Github API indeed has the possibility to do this, but it will require some special coding. Not sure we will have this in place the day musescore.org gets migrated, but for sure some time after.
Comments
I've tested on 2.1-dev, and I don't experience this bug. I only experience this in 2.0.3
BTW, before you report a bug, please test it on a nightly: https://musescore.org/en/download#Nightly-versions
Also you should try to always attached a score allowing others can easily reproduce the bug to verify.
Better mark this issue as closed, instead of path ready to be committed, as we can't reproduce this anymore on the upcoming 2.1 release.
@ ᆞᆞᆞᆞᆞ you can help test 2.1 release via https://musescore.org/en/download#Nightly-versions (check for 2.1 in the filename)
(oh, my bad, thought I selected closed in the status drop-down menu)
This is actually a duplicate of a fixed bug https://musescore.org/en/node/177586 Slurs disappear, in the most cases, after editing and Escape if the bordering note values are different
Or #177586: Slurs disappear, in the most cases, after editing and Escape if the bordering note values are different
How do you make the issue with the name one like you did, rather than copy and paste the URL then the title like I did? It will be less confusing if I can do that and it will be less likely to have duplicates (such as this).
enclose #issuenum in brackets [ ]
@mike [hashtag + id] > [# 184121] (without the space between the hashtag and id)
got it
Check the "Input Format" below a reply
On that note, if/when the issue tracker is retired and we use GitHub, I hope you can do some special coding for the new MuseScore.org to similarly display GitHub issue links according to their current title and status.
@Isaac Github API indeed has the possibility to do this, but it will require some special coding. Not sure we will have this in place the day musescore.org gets migrated, but for sure some time after.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.