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

[MU4 Issue] Overlapping dots in chords. #12494

Open
miron-flyers opened this issue Jul 21, 2022 · 5 comments
Open

[MU4 Issue] Overlapping dots in chords. #12494

miron-flyers opened this issue Jul 21, 2022 · 5 comments
Assignees

Comments

@miron-flyers
Copy link

Describe the bug
The dot of one note in a chord gets hidden by the dot of another note in the same chord

To Reproduce
Steps to reproduce the behavior:

  1. Create a new score
  2. Write the "third + second" dotted chords starting from any line of the staff (pic. 1) or write the "second + second" dotted chords starting between any two lines of the staff (pic. 2)
    1
    2

Expected behavior
It is assumed that there should be as many dots as there are notes. It can be fixed with X button but I think it should work by default.

Platform information

  • OS: Windows 11

Additional context
I'm not sure how it should look right, but the Finale does this:
3
And it is possible to fix "third + second" chords in MS4 but the only way to fix "second + second" chords looks like this:
4
which is different from the Finale option.

@HemantAntony

This comment has been minimized.

@miron-flyers miron-flyers changed the title [MU4 Issue] [MU4 Issue] Overlapping dots in chords. Jul 21, 2022
@wizofaus
Copy link
Contributor

Pretty sure it's standard for dots to shift "down" as necessary if there are clusters in a chord when the bottommost note is on a staff/ledger line, but if it's between lines, dots should shift "up"?
The chords in the 2nd measure of the Finale example look wrong to me...

@oktophonie
Copy link
Contributor

oktophonie commented Jul 21, 2022

Fixing the third+second chords is very simple, so I'd propose doing that much now.

For the rest, a proper solution would be more complex and require new user preferences to define the expected behaviour, so is certainly a 4.x feature, particularly since this is not a regression. For now the user can move the dots manually in these situations. Not ideal, but it works.

@oktophonie

This comment has been minimized.

@oktophonie oktophonie closed this as not planned Won't fix, can't repro, duplicate, stale Jul 21, 2022
@Jojo-Schmitz

This comment was marked as outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In the further future
Development

No branches or pull requests

6 participants