re. UI INFO SAVE/RESTORE
track-heights do depend on the number of tracks you have in session, so it's stored on the session file; all other UI sizes and positionsare stored in the local configuration file, when applicable. unfortunately, track-column widths are not stored in either way, so they get their original size and positions as they were hard-coded, on every program launch. this has been like so ever since... you're the first one to touch that topic :) i'll see if i can do something of the sort. however, rest assured as these column-widths don't depend on any session content whatsoever, they will get stored on the global config.
[UPDATE:] on the first commit of the year, column widths are now persistent (qtractor v0.6.4.12 git [c282d7]).
re. MULTIPLE TRACK SELECTION
i'll have to check myself whether there's a specific design/technical/amount of work reason for not having this in a near future. i'll check priorities too ;)
hi yuba,
re. UI INFO SAVE/RESTORE
track-heights do depend on the number of tracks you have in session, so it's stored on the session file; all other UI sizes and positionsare stored in the local configuration file, when applicable. unfortunately, track-column widths are not stored in either way, so they get their original size and positions as they were hard-coded, on every program launch. this has been like so ever since... you're the first one to touch that topic :) i'll see if i can do something of the sort. however, rest assured as these column-widths don't depend on any session content whatsoever, they will get stored on the global config.
[UPDATE:] on the first commit of the year, column widths are now persistent (qtractor v0.6.4.12 git [c282d7]).
re. MULTIPLE TRACK SELECTION
i'll have to check myself whether there's a specific design/technical/amount of work reason for not having this in a near future. i'll check priorities too ;)
cheers