Navigator not memorizing multiple score positions

• Jan 2, 2019 - 18:55
Reported version
3.0
Priority
P0 - Critical
Type
Graphical (UI)
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

There is a bug when I'm using the "Navigator" and "Documents side by side"(or Documents stacked) at same time.

Steps to reproduce:
1. Create two new scores
2. Show documents side by side (or stacked)
3. Select a measure (or an element) in a score
4. Move the view position in the Navigator

Expected (like as in Musescore 2.3.2):
Only the view position of the score that the selected measure is in moves.

Actual:
Both of the scores' view position moves.

OS: macOS High Sierra (10.13), Arch.: x86_64
MuseScore version (64-bit): 3.0.0.20137, revision: c1a5e4c


Comments

Title Issue with moving positions within Navigator while showing documents side by side Issue with moving positions within Navigator while editing multiple scores

Looks like the Navigator is not memorizing the positions of multiple scores.
Steps to reproduce:
1. Create two new scores
2. Move the view position of a score in Navigator

Expected (like as in Musescore 2.3.2):
Only the view position of the score that is showing moves, and the score that is not showed doesn't move.

Actual:
Both of the scores' view positions move.

Title Issue with moving positions within Navigator while editing multiple scores Navigator not memorizing multiple score positions
Priority P0 - Critical

To be clear, then, it's not just about stacked / side-by-side view, but also occurs when changing tabs. Basically, when switching from one socre to another, the second score is forced to the same relative position as the first.

I also confirm this bug. Besides being very upsetting when it changes somthing that is not visible, so one cannot understand what happened, it completely jeopardizes the use of side-by-side scores, where one wants to compare some part of a score with other part of the same or other score

Regression Yes No

Oh good, I'm not nuts, this actually is an issue. Any progress on this? I just downloaded MS3 this week and am loving most of the updates, but this one is incredibly frustrating.

I don't that know anyone has looked at this, but hopefully that happens.

Meanwhile, though, consider alternatives to the Navigator. It isn't really expected that people would be still by relying on it much given all the other ways to navigate a score that were introduced over the years (eg, timeline, search, scrolling via mouse wheel, page up/down, etc).

In reply to by Marc Sabatella

I insist, as I've said some time ago, the most useful tool to navigate through any document is a scroll bar, since with a single mouse movement one can get anywhere in the document. The navigator (which I guess has been borrowed from Sibelius) has several drawbacks. First, it has to draw a complete miniature of each page, which almost duplicates the graphic load reducing the overall performance exasperatingly. Second, except if reduced to almost zero height, in the case of a 50+ page score there is no room to show all pages so anyway a scroll bar is required.
The timeline, in turn, is of limited use. It has too much information (which most of the time is unnecessary) to just use it for navigating the score and it occupies too much space. Many users are using laptops, where the screen space is at a premium.
The mouse wheel is a good option for short-range navigation, the PgDown/Up is also useless when one needs to go back and forth, say, 40 pages. The search engine requires to introduce a measure number (or may be a rehearsal mark) the user may not know, so the approach is bisecting through an approximate guess. The scroll bar is optimum at this. It requires minimum space and it allows both short range or long range jumps.
I don't say to discard the existing options as many people may feel comfortable with them, but to add something as simple as a scroll bar.

"The timeline, in turn, is of limited use. It has too much information (which most of the time is unnecessary) to just use it for navigating the score and it occupies too much space."

Are you aware that you decrease the size of the Timeline, by clicking on the Up arrow (after hovering with the mouse) in the "Measures" box, ie Collapse Meta Rows? (image below)
And so then, you can also reduce the Timeline panel easily, as you do for the other panels.

collapse.jpg

No, I certainly wasn't aware, thanks. A button in a random position that tuns visible only when hovering right above is quite undiscoverable!
But anyway, even colapsed it ocupies about five times the height of a scroll bar, and to make matters worse, if the score has more than 60 measures, it includes indeed a scroll bar, but not to navigate the score but to navigate the time line!
The time line is quite a specialized tool that may be good for what it was designed but not for navigating a large score back and forth dozens of measures.

In reply to by cadiz1

OK, my fault.
But bear in mind how the psychology of an average software user works: One first tries, if fails and not VERY promising, one tries another thing. If very promising, one checks the manual. Best exmple: the first note ever: one tries to grab a note and drag it to the staff: doesn't work. The manual teaches to enable the Note entry mode. The timeline doesn't look very promising if the only thing you want is to navigate the score after entering several pages of music.

In reply to by Marc Sabatella

Marc, yes, I know, but having to enter a number is a good solution in a limited number of situations, for instance, having to go once and again to a specific measure (handy especially if the number is kept in the dialog list, which really happens). Regularly I don't recall the page or mesasure number where I need to go, but have a rough idea in an analog scale where it may be. The scroll bar is by far the best tool for this kind of mental framework.

I'm not opposed to scroll bars, and I'd welcome the contribution of any programmer who decided to add that as yet another option. But my comments here are just trying to help people make the best use of MuseScore today.