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

Appended text frame disappears with Navigator open #21720

Closed
MarcSabatella opened this issue Feb 27, 2024 · 1 comment · Fixed by #22422
Closed

Appended text frame disappears with Navigator open #21720

MarcSabatella opened this issue Feb 27, 2024 · 1 comment · Fixed by #22422
Assignees
Labels
P2 Priority: Medium regression MS4 Regression on a prior release UX/interaction

Comments

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Feb 27, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

If the Navigator is open while appending a text frame, the frame disappears, either immediately or upon adding text.

Steps to reproduce

  1. New score, Treble Clef template, all defaults
  2. Enable View / Navigator
  3. Add / Frames / Append text frame

Result: score scrolls to bottom of page but no text frame is visible. Or, if the frame does display - which it might in continuous vertical view - try double-clicking it and typing some text. The frame will disappear at that point.

In at least some cases, depending on whether the Navigator was open and closed previously, one might not always see this, so if you have trouble reproducing, close MuseScore completely and repeat the above steps before doing anything else. At first it seemed the issue was confined to cases where the Navigator is set to open by default (because it was open when MuseScore was last closed), but I think that was a red herring. I can reproduce this 100% of the time if I start MuseScore without the Navigator as per the steps above.

Note the frame is added, and it may reappear if you then trigger a relayout via an edit.

This seems possibly related to #14970, and who knows, maybe even to #15591

Screenshots/Screen recordings

Screen.recording.2024-02-27.7.53.41.AM.webm

MuseScore Version

OS: Debian GNU/Linux 11 (bullseye), Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230938, revision: github-musescore-musescore-d757433

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Debian 11

Additional context

No response

@muse-bot muse-bot added regression MS3 Regression from MS3 (3.6.2) UX/interaction labels Feb 27, 2024
@bkunda bkunda added the needs info More information is required before action can be taken label Mar 1, 2024
@zacjansheski
Copy link
Contributor

Looks to me like a regression that occured between 4.1.1 and 4.2

video1164622465.mp4

@zacjansheski zacjansheski added regression MS4 Regression on a prior release and removed needs info More information is required before action can be taken regression MS3 Regression from MS3 (3.6.2) labels Mar 1, 2024
@zacjansheski zacjansheski added the P2 Priority: Medium label Mar 1, 2024
@Eism Eism assigned mikekirin and unassigned Eism Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority: Medium regression MS4 Regression on a prior release UX/interaction
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

7 participants