Vertical continuous flow in handbook

• Nov 14, 2015 - 19:48
S4 - Minor
open issues

Hi everyone.

It would be so good if we'd have a vertical continuous flow view, like one were reading a pdf for example, for use when for example one is transcribing a score into MuseScore from a second file on the right side while MuseScore is open on the left side.

Please don't ask any stupid questions as to why I'm asking for this feature.



No, side by side is not the answer and I don't want to use the forum as this is a benign feature request.

Side by side puts things HORIZONTALLY side by side.

Do you know what the word vertical means?

Oh, nice then, perhaps merge or tie these two threads then?

No currently available options meet the need I am referring to.

I think some people on this forum simply don't understand English. Maybe it's not their first language.

Status (old) active fixed

This is actually already implemented as an option in nightly builds for MuseScore 2.1. It's rather buggy (which is why it's only in the nightly builds), but you can try it out in the Canvas section of the Preferences.

Also, Shoichi is Italian, but more often than not his answers on the English forums are exactly what the user is looking for.

Yes, there are *many* non-English speakers in the world, and many of them post here.

And for the record, people responding to a thread here have no way of knowing what otpions you have tried or not tried already.

So please, let's try to be polite.

Title Vertical continuous flow? Vertical continuous flow in handbook?
Status (old) fixed active

Oh thank God, that was all I was looking for.

I was indeed on the latest nightly build, but was looking under View for a setting like this.

I understand Shoichi has helped other users, but to me it is simply annoying when someone simply does not understand what one is asking for.

It is akin to bad technical support from some company that has outsourced customer services to India...

Since this already exists, I'll close this.

Again, if someone could update the handbook on this, that would be great.

I don't have time to but also I've never updated it and don't want to break any guidelines in terms of formatting and all of that.


How do I edit the main thread post so as to reflect changes?

I thought changing things here in the comment in terms of category and status and such will change the first thread as well, but it seems that is not the case.

Oh, actually it did change, I was just looking for a change I didn't actually make.

Anyways, thanks you all for your help.

For the record, there is nothing impolite about not assuming you have read every single sentence of the Handbook and tried every single available option. Lots of people fail to read the Hanbdbook cover to cover before asking questions. So pointing out things that someone might have missed is a *good* thing. It might not have helped in this particular case, but it does in very very many cases. So I would never discouraging people from offering help - regardless of their native language. Over time I think you will find the worldwide community of users to be an asset. FWIW, none of the core developers of MuseScore are native English speakers.

Title Vertical continuous flow in handbook? Vertical continuous flow in handbook

One of several features not yet present in a stable release that should be kept track of at For the moment, I'm trying to find the commit that added this and the original issue in the tracker.

None of the core developers of MuseScore are native English speakers? You've got to be joking me! That is indeed simply unbelievable.

Yet English is the lingua france of this forum.

What a facepalm revelation.

But still, I always find it annoying when I ask for help and people tell me to try the first thing that was obvious to try...

Anyways, at least a resolution has been found.

I wonder though, could we have a tick for "I've searched the handbook, website" in terms of threads so as to let users already know that one has searched for answers before posting?

It might even make people actually check the handbook before they post a request.

I wonder, how about actually making that be a mandatory tick before one makes a post? It might make for a tidier forum!

Oh, ok, that link is helpful.

But I still think the best place for that type of option to be would be under the View option, because, that is obviously where people will check first.

And canvas isn't as immediately descriptive so as to make the user realize that it is view options that it is dealing with. It sounds more like adjusting background colours, which I guess it is in the end.

I am not sure why you find it so hard to believe none of the core developers are native English speakers, but it is true.

As for a way to say you've already looked for information, we still have no way of knowing how hard you looked. After all, you yourself have also posted question that would have been answered by reading the handbook more carefully (eg, how to properly extend hairpins). It's a big complex program with lots of features and no can reasonably be expected to have read the entire Handbook cover to cover before being allowed to ask a question. Please, just graciously accept help when offered even if it turns out to be not helpful, and even if you find it annoying, keep it to your. *Others* may still appreciate the help, so please do not discourage people from offering it.

MuseScore team: Werner Schweer (Germany), Nicolas "lasconic" Froment (France), and Thomas Bonte (Belgium). All 100% fluent in English, though. All awesome people, too. ;-)

Hairpins behave counter-intuitively, hence the confusion.

I'm not discouraging help, just clutter.

It's not that it's hard to believe, it's just a facepalm revelation to me that they aren't.

Help is help, clutter is clutter.

Status (old) active postponed

Let's stay on the topic guys. Vertical continuous flow isn't ready yet, so no reason to put it into the handbook yet, otherwise people will get confused. You may of course add a comment on this topic doing a best effort of what can be added into the handbook when the next version of MuseScore comes around.

I've tried it and it works perfectly fine.

How will you get people to test something they do not know is there?

Isn't that the point of the nightlies?

Since it's not in an obvious UI place (it should really be under View) how on earth will anyone find it without going through the painstaking process of having all of the above conversations?

If you want new features tested, they should be advertised. Or at least be in an intuitive place where people expect it to be by default.


It's not a new feature. It's a potentially future feature. And yes, there are problems with it—one that I haven't yet created a bug report for has to do with the apparent anchoring of objects (the dotted line that shows when you drag them). It's not ready for prime time. That's the point of nightlies—they're not meant to be advertised.