don't merge rests for cmdJoinMeasure or cmdSplitMeasure. Keep original rest elements.
If I take two measures of quarter rests:
and join them in 2.0.3, I get
whereby it combined all 8 quarter rests into a "Measure Rest" of duration 8/4. Which I don't like (and mike320 seems to agree with me) because have "lost" information about how the space was divided up. I believe MuseScore should presume that the individual rest elements were deliberate.
Another example with notes in those measures:
The result of join measure again merges those rests together, producing something that is not nice to read:
If user actually wanted to merge those rests, then after joining the measures they can do that as a separate step by selecting those rests and deleting them. The semantics of "Join Measure" shouldn't mean anything more than join measure.
(Note, I'm not quite sure best thing to do when joining two measures containing only measure rests. I find the 2.0.3 behavior of merging them into a larger measure rest confusing because the result is a measure rest for a measure whose actual duration is different than it's time signature, so just from reading the ink, user would not know what .)
Similarly for cmdSplitMeasure, if take measure of quarter rests:
And then I split in the middle, the result in 2.0.3 is to produce a measure rest in each new measure:
This is especially confusing because "measure rests" look the same as "whole rests". Again, I think the "Split Measure" command semantics shouldn't mean anything more than to split the measure.
Note that for the case if the measure being split was already a measure rest, there is a separate feature request #166096: Make individual beat rests when splitting a measure which I agree with.