You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm about top line in both performer and composer, where instrument changes are marked. The only way to see, what instrument is set in some non-current area, is to set position to that area. The better solution, imho, is to show names after flags on top line. Too long labels may be cut, but have tooltip, exposing it in full length.
And more over, when name of some next instrument has initial words same as previous, only different part could be shown, when common part is hidden by ellipsis or even cut away.
Some kind of such bar (though implemented in other way) i have seen in BRELS MIDI Editor, which is under GPL, but only for win (honestly i don't use win stuff at all, but tried just for lulz and test to setup complete studio under wine, using minimum of non-free components).
The text was updated successfully, but these errors were encountered:
Upd: This solution also should eliminate need for top toolbar with name of current patch.
For leftmost area, whose start point is out of visible range, flag and label may be placed in begining of edge, probably with other look — to differ it from others (may be dimmed or colored, etc).
I'm about top line in both performer and composer, where instrument changes are marked. The only way to see, what instrument is set in some non-current area, is to set position to that area. The better solution, imho, is to show names after flags on top line. Too long labels may be cut, but have tooltip, exposing it in full length.
And more over, when name of some next instrument has initial words same as previous, only different part could be shown, when common part is hidden by ellipsis or even cut away.
Some kind of such bar (though implemented in other way) i have seen in BRELS MIDI Editor, which is under GPL, but only for win (honestly i don't use win stuff at all, but tried just for lulz and test to setup complete studio under wine, using minimum of non-free components).
The text was updated successfully, but these errors were encountered: