I think I’ve read it somewhere else on this forum - imho, would be great to replace Split panes (essentially two windows) rather with some “pinning” of tracks in the upper area (similar to what Excel does, or the Mixer with the zoning), so the selection works better.
The current implementation is very confusing, esp. when selecting (tell me if I do something wrong): if I have split panes in project window, and select something in the upper pane, then in the lower, the upper stays selected. So any action (coloring, deleting, etc.) is applied to both…
Is this standard Windows (or Mac) behavior? It is a bit confusing, as I would’ve expected a multi-select only to happen when pressing Shift. Quite frequently happened that I accidentally deleted something also in top row…
If you do this, you can see the dotted or the full white frame. The full one says, in which of the list the focus is. Then all actions, which are selection dependent are going to be applied to the objects selected in the given (foccused) part.
Thank you for the answer, @Martin.Jirsak . Sorry for not being clear: I know Divide Track List. I just find the implementation very clumsy compared to e.g., how the Mixer panel is doing zoning (or Excel pinning rows): if you select an event in the upper pane, and then one in the lower pane; the first one stays selected, and if you don’t pay attention (= actively de-select) changes like color/deleting, etc. is applied to both.
Clearly not the most high prio feature - just saying it doesn’t feel intuitive for me… The least I would’ve expected that only Shift+select does multi-select (as if you have only one window), but a zoning feature like Mixer console would be even better…
This behavior, of automatic double selection above and below, caused me to mistakenly delete several tracks in many projects… and I didn’t understand why!
Yes, it would be useful if there was a constraint (shift command) to select above and below!
Just to chime in - yes, this is poorly designed. It might “work as designed”, but that doesn’t mean the UX is any good. Like other commenters on this thread, I too have often accidentally done something bad because, say, something is selected in the upper pane, yet the lower pane was in focus, and I did something I didn’t mean to do to the thing in the upper pane. Trying to color a track in the lower pane while a marker is selected in the upper pane would be one example of that.
It’s little things like this that make Cubase more puzzling than it needs to be, and these aren’t expensive, difficult improvements to make.
Glad I’m not the only one… I’ve also mailed Steinberg separately… let’s hope this goes somewhere with enough upvotes.
Having zones/split panes is extremely helpful, but indeed, the UX is not well done in this implementation…