[can't reporduce now] new MuseScore process upons when open new file from desktop (on Windows store app 2.2)

• Apr 7, 2018 - 02:56

The old behavior I remember is that when double click a file outside of musescore, that musescore would open the file in the currently existing musescore process. But what I'm noticing now is that a new MuseScore process is started. So now I have multiple MuseScore 2.2 windows open.

Not necessarily a bad thing. Just I expect the same behavior.

[Edit: I can't reproduce now...will investigate later]


Comments

Downside of having a new process is that it takes a few seconds to startup and now preferences might not be synced between the processes...which might cause strange behavior. Also there are a lot of windows to manage.

I should also note that if I start without any musescore window open and select multiple musescore files in file manager and right click and press open, only one file opens.

However if I already have musescore window open, then I am able to simultaneously open multiple musescore files.

Not a biggie...but would be nice if could start musescore by opening multiple files.

Still trying to reproduce my original bug.

In reply to by ericfontainejazz

I guess this is due to how MuseScore got added to the registry:
"C:\Program Files (x86)\MuseScore 2\bin\MuseScore.exe" "%1"
Maybe turning that into the following helps:
"C:\Program Files (x86)\MuseScore 2\bin\MuseScore.exe" "%*"
I just tried, and it does not work :-(, so I think musescore doesn't expext more that one (score) filename in the command line, so simply ignores all but the first.
Need to investigate, and if that is the case we'd probably need to a) fix musescore and be the way it gets enterd into the registry

In reply to by ericfontainejazz

As far as I decipher the code logic, MuseScore should handle multiple files on the command line (it is doing a app->sendMessage(fi.absoluteFilename()); for every remaining argument on the command line, after the options, i.e. not starting with -). And that %* doesn't seem to work at all, or not the way I though it would.

In reply to by ericfontainejazz

Using 2.1, I have seen this happen and I consider it a bug. I don't know why it happens and have no idea how to reproduce it. The problem is that the second window is opened with the exact same score as are already open and the extra score is also open. I'm afraid to make any modifications to the scores when both windows are open out of fear that they will be saved as nothing but zeros and I will lose them.

Could be you actually have one "2.2" process that is actually your own development build, another that is the installed version that is the one actually set up in your file associations? Certainly it is that way for me. If I have real 2.2 running, then opening a file from Explorer opens in the running 2.2. But if I have a development build running, opening a file from Explorer naturally doesn't use that, but starts a new "real" 2.2 process.

Do you still have an unanswered question? Please log in first to post your question.