Copying a time signature causes MuseScore to shut down, on re-storing, wrong filename (with path, without dashes) created

• Nov 29, 2015 - 11:36
S2 - Critical

Max OS X 10.11.1, MuseScore 2.0.2
GIT commit: f51dc11

Sample File:

Steps to reproduce:
1. open a new file an enter various different time signature (e.g. for each bar another one)
2. copy one of the time signature and try to paste it to an "empty" bar (= bar, which has no time signature yet)

Expected result:
Create time signature in the respective bar

What really happens:
MuseScore shuts down. - When MuseScore is asked to restore, it re-creates the previous file with the path name (at least in Mac). Please look at the file name in the tab of the following 2 images:

Bildschirmfoto 2015-11-29 um 12.32.08.png

Bildschirmfoto 2015-11-29 um 12.32.30.png

The latter should probably be a separate bug report?

Thank you!


Just tested with MuseScoreNightly-2015-11-24-1120-7321ba6.dmg - and both problems aren't any anymore. But, from what I understand, there could be a 2.0.3 release, but nightly builts will be 2.1s, right? So I don't know if this issue should be closed or not...

The fact that after crash recovery you get a file with explicit path info by default is currently by design, I guess maybe to prevent you from accidentally overwriting a known good copy of the file with a questionable one. There has been been some discussion on the forum about whether there are better ways of dealing with this but nothing decided conclusively that I recall. Feel free to find that discussion and join in, or start a new one.

Thank you for the information! If it's by design, then there is no need to start a new discussion, in my opinion, since it serves it purpose very well. (Maybe mentioning it somewhere in the manual would help those like me, who wrongly think that it could be a bug, since it is an unusual solution compared to other software...)