If you've got multiple sends, FX parameters, etc. shown in the TCP, they seem to always populate "vertically first".
i.e. the columns fill before the rows. Example just using sends (red arrows show order in which slots are populated):
(Please ignore the rubbish broken WIP theme used for screenshots here, thx)
My question:
is there any way to tell these slots to populate row-first?
i.e. so you'd end up with something like this instead (mock-up):
Having searched the forums, WALTER docs, etc,.
I think the answer is currently "no". If anyone can confirm that, I'll get ready to post this as an FR instead.
(PS, I'm aware that if the track height is small enough to force the slots into one row, they will of course populate this row as expected):
---
The reason I'm interested in this:
I tend to keep tracks small (low height), but wide-ish, and I like to squeeze as much information/UI control into this space as possible. So I've got more width than height to play with.
I guess column-first takes after a tradition set out by other DAWs? It feels easier for me to parse at a glance when tracks are taller (creating more room for slots):
But like I say, I'm rarely in this view - and wouldn't want column-first vs row-first automatically changing as I zoomed tracks, of course! (Though some people might.. maybe it could be a setting/WALTER-able thing?)
PPS: if "rows-first" was an option, this final screenshot would look different: there would be three columns instead of two, because the slots would attempt to fill the width before the height. Hope that makes sense!