[Trunk] Untitled score doesn't save
1. Create score.
2. Enable 'Note Entry'.
3. Add notes.
4. Disable 'Note Entry'.
5. Close.
6. Save.
Expected result: Window appears prompting you with title and location selection.
Actual result: Score closes without saving.
Discussion: Marked as critical, because you lose the score.
Using MuseScore 2.0 Nightly Build (4789) - Mac 10.6.8.
Comments
Similar to #12648: [Trunk] Quitting, then cancelling to an unsaved score quits MuseScore
Not confirmed under Ubuntu 11.04 (latest Qt SDK, Qt lib 4.7.4)
Specific to Mac?
I was able to reproduce in Windows 8 with the latest Nightly (1f5b2451d).
I tried to send a pull request with a tentative fix:
https://github.com/musescore/MuseScore/pull/405
probably there could be a more elegant solution.
Fixed in eb4b94a2dd
I fixed it in eb4b94a2dd, hopefully in an elegant manner.
Thanks Nicolas for the fix. I was not daring modifying the saveFile function :-)
However, the saveFile() works only on the "current" score. If you open a score and a new one, then modify the new one, switch the view to the other score and then click on the "x" of the tab for the new score (without this one being in view) weird things happen.
Similarly if you close MuseScore with the tab of the new one not in front view.
Moreover, if the new score has parts and the main score of the part is not in view (i.e. you have a part in view), only the part is saved and not the main score (+parts). That's why in the pull request I had added those lines switching the currentView. I couldn't find a simple way to switch to the main score of a score with parts: I found that I had to switch to the score, set excerpt to 0 and then switch again to the score in order to actually update the view.
OK I overlooked some part of your bug fix. Sorry for that. I pushed another fix in 8bacfc8a92 It should work, and doesn't require to mess with the tabs.
Automatically closed -- issue fixed for 2 weeks with no activity.