Custom Columns Comment (improvement)

[Balderstrom]

With the recent change to File Comments (in v7.x) that allow for multiple lines, I'd like to see an improvement to how Comments are displayed within a Custom Column.

The only option now is: [=tc.comment]

The two ideas I have:

1. Ability to specify a line number (or range) to Display : Else Display Default Range if doesn't exist:
   Example (possible) syntax: [=tc.comment.line.[ #Start [-#End ] [: #Start [-#End ]] ]
   • [=tc.comment.line.2-3:1-2] :: Display lines 2-3 (if they exist), else 1-2.
   • [=tc.comment.line.2-2:1] ::::: Display lines 2-2 (if it exists), else 1+.
   • [=tc.comment.line.3:1] :::::::: Display lines 3+ (if it exists), else 1+.
   • [=tc.comment.line.4] ::::::::::: Display lines 4+
2. Search for a string to start from : Else Default Range if String doesn't exist.
   Example (possible) syntax: [=tc.comment.find.[ "STRING" [ .#AdditionalLines ][: #Start [-#End ]] ]
   • [=tc.comment.find."FooBar".1] ::::: Start Display on the line that contains Foobar & Only Display that 1 line.
   • [=tc.comment.find."FooBar".0] ::::: Start Display on the line that contains Foobar & Display all lines after.
   • [=tc.comment.find."FooBar".0:1] :: Start Display on the line that contains Foobar & Display all lines after, else Line 1+
   • [=tc.comment.find."FooBar".0:2-3] :: Start Display on the line that contains Foobar & Only that line, else Lines 2-3.

A further complexity could allow for multiple else ":" branches, that would be processed if the previous is false. I.E.
[=tc.comment.find."FooBar".0:2-3:1] :: Start Display on the line that contains Foobar & Only that line, else Lines 2-3, else line 1+.

[MVV]

WDX interface doesn't support such fields.

[Balderstrom]

Which fields, the specification of "String" within quotes or the possible syntax using colons. Current Custom Column fields use peiords, colons and slashes.

[MVV]

AFAIK content field names cannot be modified, they are given by plugin and not by user, TC just shows them and lets to use them, but TC can't pass to WDX plugin some extra field name. So it is not possible to search for text w/o interface modification.

[Balderstrom]

If I get what yer saying, then... some content field names are modified: i.e.
[=tc.writedate.M/D/Y hs] OR
[=tc.creationdate.M/D/Y hs]

It at least acknowledges varied format/strings.

This idea would be for TC to (at least) acknowledge number inputs. It has to parse the Comment already to display it, thus this would just limit what is displayed.