Navigator issues
Reported version
3.0
Type
Functional
Frequency
Many
Severity
S4 - Minor
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
Whether I'm working in continuous or page view, the navigator can't decide which size it wants to be and sometimes becomes tiny and hard to work with. Then when I try to adjust the space the navigator works with on the bottom of the screen, it sometimes jumps back to full size, but then it inevitable reverts to tiny again at some later point. This is annoying especially in continuous view because it leaves a ton of empty gray space for me to work around in the navigator bar.
| Attachment | Size |
|---|---|
| TLL strings only.mscz | 51.49 KB |
Comments
Is there any way to figure out a precise series of steps we can follow that are guaranteed to reproduce the problem? Failing that, could you perhaps record a screenshot video showing this in action?
It certainly is the case that a navigator size that makes sense in continuous view often won't still make sense in page view and versa, so you probably would want to resize it if you change views. But it shouldn't be changing size on its own, and I can't seem to make that happen in my own testing.
BTW, make sure you are on the current build, the release candidate just released today!
I've got this too - my stats are
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4747, revision: 96c1f7b
The issue appears when I press save, as well as randomly as well - I think it's when the entire page gets redrawn? See attached gif for the bug appearing in continuous view. The way I did it was: 1. resize navigator until full size 2. make an edit 3. press save.
This was reproducible numerous times, and with both ctrl-s and the save button.
In reply to I've got this too - my stats… by jameskungch
Please note also that the navigator when bugged also doesn't show the entire piece when bugged/zoomed out - see attached screenshot.
3.0.0.4747 is 3.0RC, the final release came out 2 days later and meanwhile we're even at the next version, 3.0.1, so you need to update
Have just been able to reproduce this using the exact same steps on the latest release (3.0.1.5087) as well as the latest nightly (2019-01-23-1554-master-f494c48).