"Visible" property in "measure properties" does not hide bar lines anymore (in 2.0.2)

• Jul 17, 2015 - 16:33

(2.0.2)

Unticking the "visible" check-box in "measure properties" does not hide bar lines anymore. You can see this by hiding the bar at an end-of-system measure: the bar-line is left hanging. This is different from MuseScore 2.0.1 which did (correctly) make bar lines invisible as well.


Comments

I'm not seeing this - the end bar line is hidden if the measure is in the score I just tried it on. As usual, it is always best when posting questions or problems to include the score and precise step by step instructins to reproduce the issue you are seeing.

See attached score. Try hiding an end-of-bar system. I think the bar has to have notes in it for the "bug" to display. If you delete the horizontal frame after the last bar and make the last bar invisible you should, hopefully, also see the bug.

Attachment Size
Carulli_etude.mscz 50.04 KB

In reply to by geetar

I'm a bit confused - what is an "end-of-bar system"? I thought I was hiding a measure? Which staff, and which measure?

But maybe I know what you mean - it looks like barlines remains when hiding a measure *if* they are drawn through multiple staves. If I hide measure 4 - either staff, or both - I see the barline remain. This does not happen if the barlines are not drawn through both staves. Is this what you mean? And are you sure this worked differently in 2.0.1? I definitely did some fixes having to do with barlines drawn through multiple staves, but nothing that should have affected this case. And I'm not really sure this isn't the "correct" behavior. Seems it would be expected in at least some cases, and given that, it seems better to not hide the barline by default so you can have the choice of whether or not you want to hide it. What is your use case - what are you trying to achieve?

In reply to by Marc Sabatella

Apologies, I mixed up two critical words: what I meant to write was "end-of-system bar"!

I know that something has changed between 2.0.1 and 2.0.2 because I used the hide bars "trick" to reduce the length of final systems (where it was followed by a text-frame). In 2.0.1, hiding the final bar would also hide the final bar-line, but in 2.0.2 the final bar line remains. I checked this also for the last bar on other systems: the end bar-line remains even if you hide the measure. AFAIK, there is no workaround because the remaining bar line cannot be hidden from the Inspector.

In reply to by geetar

Creating an invisible bar is definitely not the correct way to reduce the length of a system - that is what horizontal frames are for. The presence of a text frame shouldn't change anything; just add the horizontal frame first.

Anyhow, I also don't understand what you mean about inability to hide the remaining barline. Again, if you have a specific score and specific steps to reproduce a problem, let us know. But when I take your score, use Measure Properties to make both staves of the last measure invisible, then turn off the Visible property of the final barline - using either the Inspector or the "V" shortcut - it works just fine.

In reply to by Marc Sabatella

Yes, I've checked and it does work as you say – but different to the way it behaved in 2.0.1! Which is OK.

However if you hide an end-of-system measure and hide the final bar line, then press UNDO twice, it will only make the bar line visible again. However, when you then go into measure properties you will see that the visible boxes are ticked and you have to exit the box to make the bar visible again.

In reply to by Marc Sabatella

Relevant to this thread, can anyone with 2.0.1 confirm or deny the following:

1) New score, Piano template (should created two staves with barlines extended through)
2) Right click measure 1
3) Measure Properties
4) Uncheck "Visible" for top staff
5) Apply
6) Click right arrow at bottom of dialog to move to measure 2
7) Uncheck "Visible" for top staff
8) OK

Result: I think the barline between measures 1 & 2 will be still extended up despite the fact that the measures are both invisible. This is the current behavior with 2.0.2, and is also the behavior with the 2.0 release, but I don't have 2.0.1 to test with to be totally sure it didn't work differently there.

I'm working on code associated with this and want to be sure I am not missing something.

Do you still have an unanswered question? Please log in first to post your question.