Chords (and other stuff) are moved when re-opening a file

Yes, I do remember that exchange (that's how I knew MusicXML was involved, and this might turn out to be part of the key), and thank you for posting the score with the problem! Now we just need to figure out what steps you are taking to move those chords so we can understand why they aren't working. And yes, I'd fully expect if you try *any* of the things I suggested - I described quite a few separate things I tried in an effort to reproduce your problem - they will work as well for you as they did for me. but even assuming you get to work by following any of those steps, we'd still like to understand what you were trying that *wasn't* working, because I tried *lots* of things and couldn't find any that didn't work.

2/27/15 was before the release of MuseScore 2, so your score must have been produced either with 1.3 or with an experimental pre-release version of MuseScore 2. That could also be part of the problem.

The Inspector is not the only way of moving things in MuseScore 2 - the methods that worked in 1.3 *also* works in MuseScore 2 (drag one by one, or shift+drag a multi-selection, although that's less than ideal). The Inspector is jut an *additional* way that is often far more efficient and accurate. There are other ways as well, including nudging with the cursor keys (another huge improvement of MuseScore 2 over 1.3 - many more elements can be nudged using cursor keys).

MuseScore 2 provides a number of useful tools for manipulating voices. See for instance the voice buttons on the toolbar (select notes, press vocie button to move them to that voice if there is empty space available), also Edit / Tools / Implode, Edit / Voices.

Yes, the spacing of staves is larger. i have no idea what you used to generate the "before" image, but it looks like it was maybe created with MuseScore but using different style settings. Again, the settings in your score are different from the defaults, and that is why the spacing is larger. Trying creating a new score from scratch and then checking out the settings for lyrics in Style / General / Page and Style / Text. Then copy those same settings to your score. Again, you must have either inadvertently changed them, or somehow they got set from the MusicXML file you imported, or they are left over from an earlier version of MuseScore.

Dragging rests offscreen is a definite no-no in any version of MuseScore. In order to understand why these rests are there and how you would need to fix it, we'd need you to start another thread and post the score you are having trouble with (probably the MusicXML file itself would be most useful).

Regarding style settings, there are obviously quite a lot of those. if you have specific questions after reading the relevant Handbook sections (yes, your note to self is good :-), feel free to start another thread and ask away. It's always best to use separate threads for separate questions, makes the discussiosn 8much* easier to follow.

It's normal that MuseScore 2 will prompt you to save any score created with an older version. The idea is, it has to "convert" a lot of older things to the newer format, so it already has done some work for you. That is basically what it is offering to save. It's up to you whether or not to take advantage of that.

I can see now that your score with the "messed up" chords *was* in fact created with 1.3. So, I opened that score with 1.3, and sure enough, it looks more or less exactly the same - the chord symbols are overlapping the staff just as they are in 2.0.3. And then they jump up above the staff as soon you do anything. Not sure what is going on here, but clearly there is a bug in 1.3 that causes the chords to move from the "wrong" to the "right" position. 2.0.3 seems to have fixed the bugs in that the chords don't move after loading, but unfortunately, that means they are now stuck in the "wrong" place.

So whatever problem you are having, it is *not* a case of edits made in 2.0.3 not saving - you had apparently never in fact saved that score with 2.0.3. In fact, it seems that whatever you did to that file, you did with 1.3, and 2.0.3 is showing you almost the exact same thing that 1.3 shows before the bug in 1.3 that caused the chords to jump above the staff inexplicably.

Aside from that, indeed, you will notice that 1.3 is able to fit the whole chart onto one page whereas with those same settings, 2.0.3 does not. Comparing the two, I can see that the main difference is the amount of space between the staff and the lyrics. 2.0.3 uses different settings to control this than 1.3 did - and 1.3 unfortunately had numerous bugs and limitations that caused it to ignore some settings that had been made. Now that 2.0.3 honors these settings more completely/correctly, it can sometimes happen that a score made in 1.3 will look different in 2.0.3, so you might need to weak the settings manually.

For this score, 1.3 is actually placing the lyrics closer to the staff than it should have based on the style settings, whereas 2.0.3 is honoring the style settings more literally. Quickest way to get 2.0.3 to look more like 1.3 on this score - set "Style / General / Page / Lyrics top margin" to 0sp. It's a little more complicated than in reality - 1.3 was actually more or less completely ignoring the vertical position set in the text style setting and instead *only* honoring the top margin in the general style. But there's no way to get 2.0.3 to reproduce that particular 1.3 bug, so instead of literally copying the same settings, think more in terms of the end result you want.

More generally, style settings are per score. This particular score has style settings that are a combination of whatever 1.3's defaults were, whatever it imported from the MusicXML file, and whatever changes you made. To reset all of that to stock 2.0.3 settings, simpelst would be to create a new score (or use "My First Score"), then go to Style / Save Style and name it "default.mss". Then use Style / Load Style to load those settings into your score.

However, to get those style changes to take effect on your existing lyrics, you'll have force MuseScore to apply those settings by right clicking one lyric, Select / All Similar Elements, then pressing the "Reset Text to Style" button in the Inspector. One of the great new features in MuseScore is that normally, when you change a text style, it takes effect immediately, but this won't apply to text elements originally created in 1.3, because 1.3 lacked that facility and was unable to prepare these lyrics for the auto-update. That's basically what the reset button does for you.

If you do this with your score, you'll see the default lyric size is much larger than what you were using in 1.3, and that will prevent it from fitting on one page. So right click any lyric, Text Style, and set it to 7 like you had it before. but there are other settings that also differ between the 2.0 defaults and the various customizations you had apparently performed to get it to all fit on one page, so you'd have to redo some of that way. Biggest is that you had reduced the staff size to 1.7sp. Repeating just those two settings is almost enough to make it fit again in 2.0, but there's at least one other setting you'll need to tweak: you had reduced the vertical frame lower margin (in Style / General / Page) to 1sp to redocue the space between the title frame and music, and you'll want to redo that in 2.0 as well, or use the Inspector to override that default.

Make just those few changes and it looks more or less like it should.