AddCol: In Search Field Overrides Added Columns in Defined Macros After v1396a

[SolarTheory]

This wasn't the case until versions after (v1.5.0.1396a - the last version that supported multiple AddColumn: (alias AddCol:))

The Issue: Up to and including v1.5.0.1396a: Multiple columns could be added using multiple Bookmark macros that each defined column sets.

(1) For Example: If "LinkCols:" macro is defined as: <AddCol:ReparseTarget;HardLinkCount>, and "ParseCols:" macro is defined as: <AddCol:ParseFullPath;ParseName>, entering the following into the search field would show ALL four columns defined in those separate bookmark macros: <LinkCols: ParseCols:>

(2) Version 1396a also supported adding multiple separate columns in the search query as follows: <AddCol:ReparseTarget AddCol:HardLinkCount AddCol:DateAccessed>. This helped logically when defining complex custom columns as you could group the AddColumn: part of the query with their associated formulas or functions that created them or that they relate to.

After v1396a:

• With respect to (1) above, only the columns in ParseCols: would be added, as it overrides the columns defined in LinkCols:. This appears to be search query position-based. If LinkCols: is placed after ParseCols:, then it is only the LinkCols: columns that will be added.

• Regarding (2) It appears that support for multiple separate 'AddCol:' in the search field was removed. The following syntax no longer works, and only the last AddCol: in the list is used: <AddCol:ReparseTarget AddCol:HardLinkCount AddCol:DateAccessed>. Now, in complex search patterns with custom columns and formulas, they have to be predefined together, separate from the formulas or functions that they relate to. But this issue is secondary to the change to (1) above - it is more of an inconvenience.

Was a Fix to This Attempted?
I noticed the changelog for v1.5.0.1405a included the following:

• "improved adding columns when there is an active search that changes the columns.".

Was this meant to address some of these issues? It had no link to a discussion about the change, so I do not know exactly what it attempted to address.

I have since upgraded to the latest version (v1407a), and I am testing it. But I cannot see any meaningful difference or change. It certainly as not reverted back to how v1396a behaved, it is still overriding columns when multiple macros are used in the search query when each macro has a column set defined in it.

Please consider bringing back the column add behavior we had in v1396a and prior versions.

Thanks!!!

[void]

Thank you for the issue report SolarTheory,

Everything is not calculating the string-length of columns used with the add columns command correctly.
Multiple uses of the add column command will not concatenate the column names correctly.
This issue will be fixed in the next alpha update.

[void]

Everything 1.5.0.1408a fixes an issue with adding multiple columns with search commands.

[SolarTheory]

Insane turnaround time for an issue I literally posted just a few days ago. Many thanks!