[EPIC] UI/UX issues and suggestions
Reported version
3.5
Type
EPIC
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
This EPIC issue is a place to collect bugs and suggestions that should be addressed as part of the User Interface redesign for version 4.0. Bug that are not related to UI or UX specifically should not be included in this issue.
The overall severity is set to S3-Major even though there will be a large number of suggestions and some critical issues as well.
Comments
Format => Page Size => Unit => was set to Inch. --- Inspector => Element => Offset is still mm (when I select a text).
The severity for the overall EPIC issue is Major and truly the Frequency should be none. Comments on individual issues listed here need to be kept on the individual issues. EPIC issues are a clearinghouse for issues to make it easier for developers to keep track of what we're up to here in the forums.
In reply to The severity for the overall… by mike320
Where / how should this be posted? It appears to be simple fix.
You already reported it in #310552: Page Size set to inch --- Inspector Element Offset is mm and it is already included in this list. My note in that issue put the link between it and this.
In reply to You already reported it in … by mike320
Ok, thanks! What is the correct procedure to add to the list of problems? For example, the repeat does not work.
That most probably is a known and meanwhile fixed issue (will be fixed in 3.5.1), see #308698: Continuous view stops repeats from working in playback, as you've been told in https://musescore.org/en/node/309979 already ;-)
In general see https://musescore.org/en/node/309537
In reply to That is a known and… by Jojo-Schmitz
I missed understanding that it is a known issue. I just saw a highlighted link with a strike through it. Thanks for clarifying.
When is 3.5.1 expected to be released?
When is 3.5.1 expected to be released?
Good question. No one knows.
How strict do we want to be when deciding what counts as a UX/UI issue? Some of the issues tagged seem only loosely related to UX/UI, such as #42301: Instrument Changes: add ability to change back to a previous instrument, which is really about adding a new feature (i.e. changes to code, file format, and internal model) rather than changing how an existing feature is presented to the user.
I would think such a suggestion would be something Tantacrul would implement as part of the Mixer Redesign. I would rather include something and him decide it's not part of his responsibility than to have him not think about it as part of something else he's working on.