Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect message displayed when trying to open a file which is not accessible #18025

Closed
henkdegroot opened this issue Jun 17, 2023 · 3 comments
Assignees
Labels
duplicate Already covered by another issue / addressed in another PR UI Visual issues affecting the UI (not notation)

Comments

@henkdegroot
Copy link

Issue type

UI bug

Bug description

Open a file from the Recent files option, shows an incorrect message when the file no longer exists/is not accesible.

MS checks at startup if the files in the recent list still exists or not. If they no longer exist they are removed from the list.
However if you do not close/restart MS, the file remain in the list and can be clicked.

The message presented to the user in this case is miss leading:
image

An easy/quick fix could be to update the message and include information related to a possible missing/inaccessible file.
Alternative options would be refresh the recent list more often or add a proper test for missing/inaccessible files with it's own message.

Steps to reproduce

Attach an external storage device (i.e. USB drive)
Start MS4
Create a new score and saves this to the external storage device
Close the new score
Remove the external storage device
Now use the shortcut in the recent score list to re-open the file

Screenshots/Screen recordings

image

MuseScore Version

4.0.2 + recent master

Regression

No.

Operating system

Windows 11

Additional context

No response

@muse-bot muse-bot added the UI Visual issues affecting the UI (not notation) label Jun 17, 2023
@oktophonie oktophonie added the duplicate Already covered by another issue / addressed in another PR label Jun 17, 2023
@oktophonie
Copy link
Contributor

Duplicate of #12028

@oktophonie oktophonie marked this as a duplicate of #12028 Jun 17, 2023
@oktophonie oktophonie closed this as not planned Won't fix, can't repro, duplicate, stale Jun 17, 2023
@henkdegroot
Copy link
Author

Apology for the duplicate, I did search but appearantly not good enough.

@oktophonie
Copy link
Contributor

No apology necessary, the extra context and examples are always useful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Already covered by another issue / addressed in another PR UI Visual issues affecting the UI (not notation)
Projects
None yet
Development

No branches or pull requests

4 participants