|
Post by Stefan on Nov 2, 2021 7:29:07 GMT -5
George,
I note that I can enter a line label like .-AB in the command line area and subsequently reposition to that line with LOCATE .-AB
However, the same is not true of a line TAG. A tag like :-AB is accepted on data entry, but the command parser frowns upon LOCATE :-AB (Invalid Tag Operand)
I have a macro that needs to apply persistent Tags to some lines, i.e. tags the user sees once the macro finishes. To avoid confusion with any tags the user may have already placed in the file, the macro-generate tags should use a unique format, for example :-AB
I note that during data entry, the line command field accepts just about every character in line lables and line tags as long as they start with a dot or colon respectively. So, for example, .-AB. and :-AB. are both accepted and treated as they should be. But while LOCATE .-AB. works perfectly, LOCATE :-AB. is rejected.
Suggestion: Would it be possible, for tag validation to follow the same rules as label validation, please?
I appreciate that the Parser is a complex affair and going in there is a courageous undertaking. So I understand that you may prefer not to poke about within it to widen it's acceptance of Tags.
(On the other hand, from a coding perspective, you may be able to just 'clone' the code from that used to validate labels.)
In which case, SPFLite should perhaps only accept tags within the established syntax rules in the line command area.
|
|
|
Post by George on Nov 2, 2021 9:21:46 GMT -5
Stefan: Tag validation was set to only normal alpha, but there was really no reason for it. I've removed it.
I'll post a newer Beta.
George
|
|