Need a better way to tell 1.x and 2.0 appart
If you have 1.3 and 2.0 Beta 1 installed, and want to open an mscz file, some decision needs to be made whether it is to be opend by 1.3 or by 2.0 Beta 1. This seems unvoidable, but I see some problems with that:
a) I found the defaults to be inconsistent between 2 machine, both have either version installed (plus some nighlties), both Window 7 Enterprise, 64bit, both had them installed in the same order, however on one machine 1.3 was still the default applocation for mscz, on the other it t was 2.0 Beta 1, Any idea why?
b) in the context menu 'open with' it is pretty difficult to tell the 2 possible applications apart, the only difference is the Color of the Icon, blue for 2.0, black for 1.3.
See the dialog to select the Default application
(can't capture the 'open with dislog, bit it has a similar siisue, onle the Icons are smaller))
I think the 2.0 Icon should include a 2, and/or the programs name should something like mscore2.exe
Comments
With renaming it to mscore2.exe, then scanning the entire registry and fixing all entries there (nothing for the faint-hearted), I managed to make it look like this now:
Still not optimal for 1.x, but I guess it is too late to fix that (short of hacking the registry)
It's not too late. If everything goes well, the registry keys created during the install will be deleted and recreated when the next beta will be installed.
If you want to experiment, writing to the registry is done here. https://github.com/musescore/MuseScore/blob/master/build/packaging/WIX…
Changing mscore.exe to MuseScore2.exe is also an option.
I meant too late for fixing 1.x registry keys, to get MuseScore 1.x to show up as "MuseScore 1" rather than "mscore.exe".
I had a look at the stuff you pointed at earlier today, and I believe I have something ready for this, but I haven't yet managed to the QtCreator to actually build an mscore2.exe.
And not having the tools nor knowlegd to build an installable package, I can't test this either...
Is this still a problem on Windows?
I don't think so, so let's mark it fixed
Automatically closed -- issue fixed for 2 weeks with no activity.