Instrument order not preserved in Parts chen lung • Apr 3, 2011 - 13:39 Type Functional Severity 3 Status closed Project MuseScore 1. Open score with three instruments. 2. Create Part including all instruments. Expected result: The order of original score is preserved. Actual result: The order changes. Using MuseScore 2.0 nightly build (4145) - Mac 10.4.11. Reply Comments [DELETED] 3 • Apr 11, 2011 - 17:38 Severity ⇒ i cannot reproduce this (at r4170). Reply chen lung • Apr 11, 2011 - 23:20 I've just realised you tick (or cross) the instruments in a certain order when creating a part. Maybe it's a design thing, but I think it should be more clear, or just dropped (decide the order after creating the part). Using MuseScore 2.0 nightly build (4156) - Mac 10.4.11. Reply chen lung • Jun 21, 2011 - 21:18 Severity ⇒ Status (old) needs info ⇒ active Reply Fyrult • Apr 16, 2016 - 23:03 Severity ⇒ Status (old) active ⇒ duplicate See #91271: Crash on save after creating new part from score with connecting barlines with parts selected in bottom-to-top order The decision was made to disallow having parts in a different order from score in 2.0.3 and current master. Reply System Message • Oct 31, 2018 - 09:00 Severity ⇒ Status (old) duplicate ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 1, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 2, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 3, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 4, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 5, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 6, 2018 - 09:00 Severity ⇒ Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
chen lung • Apr 11, 2011 - 23:20 I've just realised you tick (or cross) the instruments in a certain order when creating a part. Maybe it's a design thing, but I think it should be more clear, or just dropped (decide the order after creating the part). Using MuseScore 2.0 nightly build (4156) - Mac 10.4.11. Reply
Fyrult • Apr 16, 2016 - 23:03 Severity ⇒ Status (old) active ⇒ duplicate See #91271: Crash on save after creating new part from score with connecting barlines with parts selected in bottom-to-top order The decision was made to disallow having parts in a different order from score in 2.0.3 and current master. Reply
System Message • Oct 31, 2018 - 09:00 Severity ⇒ Status (old) duplicate ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 1, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 2, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 3, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 4, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 5, 2018 - 09:00 Severity ⇒ Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 6, 2018 - 09:00 Severity ⇒ Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Comments
i cannot reproduce this (at r4170).
I've just realised you tick (or cross) the instruments in a certain order when creating a part.
Maybe it's a design thing, but I think it should be more clear, or just dropped (decide the order after creating the part).
Using MuseScore 2.0 nightly build (4156) - Mac 10.4.11.
See #91271: Crash on save after creating new part from score with connecting barlines with parts selected in bottom-to-top order
The decision was made to disallow having parts in a different order from score in 2.0.3 and current master.
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.