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

Lyrics messed up when copying and pasting from another existing file in 4.4.4 on macOS #25962

Open
4 tasks done
MRoth1910 opened this issue Dec 31, 2024 · 0 comments
Open
4 tasks done
Labels
regression MS4 Regression on a prior release UX/interaction

Comments

@MRoth1910
Copy link

MRoth1910 commented Dec 31, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. Open existing file and copy notes with lyrics.
  2. Paste into a second score file.
  3. Select text to be edited.
  4. The cursor/text selection breaks. The existing text is doubled in the same box. I can't get rid of all of the existing text with cmd + a. I can't select what I want with the trackpad, because the cursor ends in the wrong place. The cursor is in the wrong place when trying to make further edits such as adding a space with option + space, when multiple words are on the same note.

Only some text is affected. The problem began at v. 5. Deleting the text fixes nothing. The problem continues even with blank boxes.

I leave the text as is and replace box-by-box in order to keep myself sane. It's easier to do that and only retype a few lines (the number of psalm verses is variable between psalms, so the last two need to be retyped, but other than that, I don't have to retype the line numbers, and it helps me to see where the accents go in case I get lost). So I should be able to use cmd + a or the trackpad to select text, hit delete, and enter what I wish to enter. See the score Psaumes_aux_vepres_Epiphanie.

There is a related issue: in the original file, this psalm was longer. Deleting the extra syllables froze the text entering feature, so I couldn't advance to the next syllable correctly (this is a problem because the hypenation is necessary and if the word is a dactyl with the first syllable bearing the Latin accent, the second non-accented syllable needs to be entered on the notehead in parentheses. See page 2 of the score entitled Saint_Joseph_aux_vêpres.

Supporting files, videos and screenshots

ms_mwe_files_dec_31_2024.zip

Screen.Recording.2024-12-31.at.13.22.31.mov

What is the latest version of MuseScore Studio where this issue is present?

4.4.4

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

macOS 15.1.1 Sequoia

Additional context

No response

Checklist

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
@muse-bot muse-bot added regression MS4 Regression on a prior release UX/interaction labels Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression MS4 Regression on a prior release UX/interaction
Projects
None yet
Development

No branches or pull requests

2 participants