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

Apply time signature after undo can produce inconsistent results #24962

Open
4 tasks done
wizofaus opened this issue Sep 29, 2024 · 0 comments
Open
4 tasks done

Apply time signature after undo can produce inconsistent results #24962

wizofaus opened this issue Sep 29, 2024 · 0 comments

Comments

@wizofaus
Copy link
Contributor

wizofaus commented Sep 29, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. Create a new score with default 4/4 time signature and fill 3 measures with 1/4 notes
  2. Select just the first two measures
  3. Apply a 3/4 time signature from the palette
  4. Note the following (4/4) measure remains as is, with an extra rest inserted in the previous (new) 3/4 measure
  5. Undo - returns to state after step 2. (first two measures selected)
  6. Re-execute step 3 (apply 3/4 time signature)
  7. Expected: should produce same result as seen in step 4
  8. Actual: result is different, with the notes from all 3 measures now spread over 4 3/4 measures followed by an empty 4/4 measure.

Supporting files, videos and screenshots

Start:
image
After first 3/4 apply:
image
After undo and reapply 3/4:
image

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

4.4

Regression

I was unable to check

Operating system

Windows 11

Additional context

Not a major issue, just a weird quirk that may be worth investigating, as anything that means "undo" isn't properly restoring a previous state can potentially lead to more serious problems.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants