-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to make Change layout the default #1
Comments
Interesting. If you click on 'Change layout', suppose the box layout mode was 'auto' but displayed in 'high' mode, then the box layout will change from 'auto' to 'large'. Note that the same mechanism is used for boxes with inputs and outputs and boxes with only inputs or outputs. For boxes with only inputs or outputs, 'High' means Title on top, 'Large' means title on side. What I could do in options is two sliders, one for boxes with inputs and outputs, and one for others. It could determinate what the 'auto' mode does, from "always large" to "always high", applying a factor to one of the areas to encourage one mode on the other. Maybe theses options are overrated... Probably pure area comparison is not a good default mode. |
Ah I see. So far it seemed that auto would always default to the layout I didn't like (is that "high"? I don't know. with ports interlaced and the smallest "width"). |
Ok, The port order is given by JACK. Here the order inconsistency comes from a2j or pipewire. Patchage does the same: I'll put the options, I think you are right and the default should be to prefer 'large' layout except if the area win is important (for boxes with inputs and outputs). Any problem with boxes with title on side (splitted boxes) ? |
Ok, you will find a combobox option in tricks tab after git pull! |
Currently you have to set "Change layout" individually for each program, plugin, device etc.
Since I want to have this for pretty much everything I do in the patchbay it would be great if this can be set as default option in the settings.
The text was updated successfully, but these errors were encountered: