Controlling "visibility" of objects - implementation is too restrictive.

• Nov 4, 2024 - 21:34

Toggling the visibility state of a given object is carried out by the "V" key shortcut.
Its logic is minded as an "on/off" flipping of the object's visibility state.
This logic is fine as long as it is applied on a single object.
.
However - when it is applied on a "selection" of objects - it brings about implausible result.
Applying it on a "selection" would flip the visibility state of each and every object within that selection.
.
Here is a common test case of mine.
Invisible "rest"-s infiltrated unintentionally into my sheet.
Upon printing the sheet they are not seen there.
As a cure - an attempt to set them all into a "visible" state would require "V" on each and every individual rest.
This is a rather tedious and impractical process.
.
Instead - one may propose two additional operators:
"Set Visible" and "Set Invisible".
These will explicitly set the visibility state of all selected objects, regardless of their current visibility state.

.
Putting this enhancement request in the DEV "wish-list" / workplan will be appreciated.

Kind regards

Hillel.


Comments

In MS3 ticking or clearing the checkbox by using the mouse, (i.e. not using the keyboard shortcut), explicitly sets visible or invisible rather than toggling the status. Perhaps this also works in MS4.

In reply to by yonah_ag

Sorry, I didn't get your point.

Here is a detailed scenario that exemplifies my case, as depicted below:

Initial condition:
Pic #1 - Several "hidden" invisible notes are scattered across few measures.

Pic #2 - All measures are selected

Pic #3 - "V" is pressed. All invisible notes turn into visible state while all visible become invisible.

This result is not good fore me.
My point is that I am looking for a way to impose visibility state on all selected objects - in a single action.

How?
Please be more specific.

Thanks
Hillel.

Attachment Size
Pic#1.png 10.27 KB
Pic#2.png 11.46 KB
Pic#3.png 11.5 KB

In reply to by Hillel

.
Well - my testcase is indeed being processed under MU-3.6.2
Following your instructions, in MU-4 it works fine for me.
Thanks.
Now - before switching the score to MU-4 (which is not portable to my team mates configuration), was this MU-4 capability implanted into your MuseScore 3.7 Evolution?

Thanks again

Hillel.

In reply to by Hillel

Yet - it does make sense to disable the "V" toggle operator, unless a single object is addressed - right?

No! It does not necessarily make sense to disable the "V" toggle when mutiple objects are selected. This toggle can occasionally be useful for toggling between scenarios and, in any case, could break other users' workflows, especially if they have incorporated such toggling into plugin code.

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