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

Regroup-Rhythms deselcts notes when selection contains a rest or when selection starts on other that first beat. #24955

Open
4 tasks done
Ash-86 opened this issue Sep 28, 2024 · 2 comments
Labels
community Issues particularly suitable for community contributors to work on regression MS4 Regression on a prior release UX/interaction

Comments

@Ash-86
Copy link

Ash-86 commented Sep 28, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. Make a selection of a phrase without rests.

  2. apply regroup-rhytms --> selection marquee is maintained

  3. replace any note with a rest within the selection.

  4. apply regroup-rhythms. --> marquee selection disappears.

    1. Make a selection of a phrase that starts on a beat other than the first.
  5. apply regroup-rhytms --> selection marquee is maintained yet the notes are deselected.

Supporting files, videos and screenshots

regroupo.mp4
regroup2.mp4

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

4.4.2

Regression

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

Operating system

windows 11

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 Sep 28, 2024
@cbjeukendrup
Copy link
Contributor

This should indeed be fixed, but to get a better view of how to prioritise this, does it cause any big problems or annoyances?

@cbjeukendrup cbjeukendrup added the community Issues particularly suitable for community contributors to work on label Sep 28, 2024
@Ash-86
Copy link
Author

Ash-86 commented Sep 28, 2024

I don't think any big problem, no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues particularly suitable for community contributors to work on regression MS4 Regression on a prior release UX/interaction
Projects
Status: Available
Development

No branches or pull requests

3 participants