Opened scores (including templates) appear twice in Start Center & recent files
Ubuntu 14.04, GIT commit: 0a6faf9
Not sure if things have stabilized to the point where it's worth filing issues, but I've noticed this particular bug since the recent changes a few days ago, I think.
1) clear recent files list from file menu
2) restart musescore to get startcenter to honor that (a bug in itself?)
3) open a score via file / open
4) go to startcenter
Result: score appears twice. It also appears twice in recent list in file menu. However, scores that were created new then svaed appear only once (these formerly did not show at all). I also note that if you create a score from a template, the template itself shows in the recent list as well (twice).
Comments
restart musescore to get startcenter to honor that (a bug in itself?)
This is already fixed.
For the main bug, I can't reproduce currently. Can you?
Yes. Could be Linux-specific, then. Anyone else able to verify? I'll investigate meanwhile.
I've found the reason I see this bug but others don't - my main MuseScore directory is a symlink to a directory on another drive. So the canonical name for most of my scores is different from the nominal name, causing the file to get added twice in the following code:
https://github.com/musescore/MuseScore/blob/1f5915ecac587307495c60a71a2…
I see that this second call to addRecentScore(path) was added to address an issue with imported files not showing correctly,a nd there was some concern about the coce at the time:
https://github.com/musescore/MuseScore/pull/1495
So I wonder, is there some other way to solve the imported file issue without breaking symlinks?
Not sure why we use canonicalPath and not absolutePath. Would that solve your issue?
Looks it solves this particular issue for me. No idea if it causes others. Still seems weird we try to add scores twice - I guess we rely on them usually be the same value?
Not for me:
http://wstaw.org/m/2014/12/20/plasma-desktopXK1927.png
http://wstaw.org/m/2014/12/20/plasma-desktopXI1927.png
Fixed in d5c3cdfeef
Automatically closed -- issue fixed for 2 weeks with no activity.