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

"Swap with clipboard" command does not work and breaks range selection #17000

Closed
MarcSabatella opened this issue Mar 24, 2023 · 1 comment · Fixed by #17332
Closed

"Swap with clipboard" command does not work and breaks range selection #17000

MarcSabatella opened this issue Mar 24, 2023 · 1 comment · Fixed by #17332
Assignees
Labels
P1 Priority: High regression Regression on a prior release UI Visual issues affecting the UI (not notation)

Comments

@MarcSabatella
Copy link
Contributor

Issue type

UI bug

Bug description

The swap with clipboard command has broken badly between 4.0.1 and 4.0.2. It correctly pastes the current clipboard contents, but rather than load the clipboard with the contents fo the destination, it appear to corrupt the clipboard in a strange way, where after attempting to paste it, nothing appears to happen, but you then become unable to make range selections until you save/reload.

Steps to reproduce

  1. new score, Treble Clef template, 4/4
  2. enter quarter notes C C C C | D D D D into the first two measures
  3. Select the first measure
  4. Ctrl+C to copy
  5. Select the second measure
  6. Ctrl+Shift+X to swap with clipboard
  7. Select the third (empty) measure
  8. Ctrl+V to paste

Result: nothing is pasted, which is bad enough, but worse, you are now completely unable to make a range selection of any kind. Clicking a measure, Click/Shift+click, Shift+Right, Shift+drag, etc - range selections just cannot be made anymore. Save/reload fixes the inability to select, but the swap operation itself will still have failed.

Screenshots/Screen recordings

Screen.recording.2023-03-24.8.54.24.AM.webm

MuseScore Version

OS: Debian GNU/Linux 11 (bullseye), Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230651545, revision: github-musescore-musescore-dbe7c6d

Regression

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

Operating system

Debian 11

Additional context

This worked in 4.0.1, but is broken in 4.0.2. It remains broken in a recent build from master.

@muse-bot muse-bot added regression Regression on a prior release UI Visual issues affecting the UI (not notation) labels Mar 24, 2023
@DmitryArefiev DmitryArefiev assigned cbjeukendrup and unassigned Eism Apr 24, 2023
@DmitryArefiev DmitryArefiev added the P1 Priority: High label Apr 24, 2023
@DmitryArefiev
Copy link
Contributor

Fixed in #17332

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority: High regression Regression on a prior release UI Visual issues affecting the UI (not notation)
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants