By logical column, do you mean the order in which the columns are declared in
columns = [
(N_('Status'), 'status'), # amd
(N_('Cat No.'), 'catalognumber'),#amd
(N_('Album Artist'), 'albumartist'),
(N_('Disc Subtitle'), 'discsubtitle'),
(N_('Track No.'), 'tracknumber'),
(N_('Disc No.'), 'discnumber'),
I’m still working out how the column setup really works. Originally when they were added here they were going to show up on both sides by design. I discussed making a separate list so that some of them would not be visible on the Left. Short of dragging the position over to the far right making that column width as small as it can be.
When the configurable columns methodology was implemented that made having two lists a moot point. So I reverted all my changes back to having the single list.
So, to have a column be present at all- it’s defined in
itemviews. Then it will display the variable
'~length', that’s been assigned to the column
(N_('Album') in it’s raw form.
Since things like artwork quantity, unsaved/changed tracks, etc. are derived from within, are dynamic, and that data is specifically shaped/formatted for display, that is done in the code segment for the level of detail that is being made visible. If at the track level, an
elif column in
elif column in
elif column == '~length':
length = self.metadata.length
In the Column Length, the value we want is
~length. We’ll call that
length and it comes from
self.metadata.length. There’s a value there, then format it
format_time(length) otherwise give me nothing
But if we wanted to see
~length as it is stored natively the whole
elif column == wouldn’t be necessary.
I need to look at
QTreeWidget and see what/how parameters are passed to it and what they do and some of this should be a clearer.
Thanks for putting up with me and my seemingly boneheaded approach to figuring all this out…
text = 'hello world'
Just doesn’t do it for me as a starting point.