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] Bug with Horizontal Frame #15943

Open
alexnoclain opened this issue Jan 18, 2023 · 1 comment
Open

[MU4 Issue] Bug with Horizontal Frame #15943

alexnoclain opened this issue Jan 18, 2023 · 1 comment
Assignees

Comments

@alexnoclain
Copy link

Describe the bug
Problems with the behavior of horizontal frames.

  • When the handle is pulled outside the page the system follows it and ends up outside the page. (issue already present with Musescore 3.6.2)
  • At the beginning of a system, when the frame is stretched, the names of the instruments remain in their original place.
  • When a horizontal frame is placed at the end of the system and is stretched, it ends up in the next system. The 2nd system is found without staves but with the names of instruments and the brace.
  • It is possible to move the frame freely in the system.
  • Sometimes deleting the frame causes a crash of the app.

To Reproduce
Steps to reproduce the behavior:

  • Create a new file with 2 instruments
  • Add a horizontal frame at the beginning and at the end of the system
  • Add a system jump on the horizontal frame of the end of the system.
  • Expand the frame in one direction and in the other
  • See the video for details

Expected behavior

  • Frames should not move freely
  • Instrument names should stay next to the system.
  • a large stretch should not cause a system jump.

Screenshots

horizontal.frames.issues.mov

Platform information
OS: macOS 12.6, Arch.: x86_64, MuseScore version (64-bit): 4.0.1-230121751,
revision: github-musescore-musescore-9b70a8c

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Apr 29, 2024

Came up again in https://musescore.org/en/node/363439
I wonder whether it has the same root cause as #19759/#22256, in that it seems a frame gets treated like a measure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants