|
|
Post by Stefan on Jul 5, 2021 7:44:30 GMT -5
George,
Sorry for the drips and drabs bugs, I know you're looking to get a new version out there...
Version 2.5.21183.... Issue with RESET ALL command
Take a file
Exclude a bunch of lines Issue RESET ALL => nothing happens Issue RESET => Excluded lines re-appear as expected
Do the same but exclude a bunch of lines AND set some line labels on others Issue RESET ALL => nothing happens Issue RESET LABEL => Line Labels are removed, as expected
|
|
|
|
Post by mueh on Jul 5, 2021 8:43:28 GMT -5
George: In addition to above Problem RESET RETRIEVE get's Invalid RESET operand - RETRIEVE .
RETRIEVE accepts RESET operand to clear retrieve cmd's but is not documented .
Thanks
|
|
|
|
Post by Stefan on Jul 5, 2021 8:53:38 GMT -5
Robert, There has been a change recently. I have v2.5.21149 running on one machine. Take a file with excluded lines AND some line labels , issue "RESET" and the excluded lines reappear and the labels stay. All good. Take the same file and issue "RESET ALL" and the excluded lines reappear AND the labels have gone. Still good.
In version 2.5.21183 this behaviour is different.
Simple "RESET" does what it used to do, and (although I haven't checked each individually) so does "RESET <keyword>", except that "RESET ALL" does nothing (again, I haven't checked it against all the various settings)
It must be a consequence of something George changed only recently. Hopefully that narrows down his search.
I don't interpret the HELP doc the same way you do. I guess ALL has two possible meanings - (1) RESET ALL features in the file or (2) RESET ALL <other operand> as in 'reset every occurrence of <other operand> in the file. In the case of (2), the ALL is redundant because RESET operates against every occurrence anyway. You cannot RESET FIRST LABEL or RESET PREV TAG. I think the HELP doc tries to make the point that RESET ALL is as per case (1) only, but the wording could be clearer.
I for one DO like the fact that "ALL means 'every feature in the edit file' It makes sense that "RESET ALL" keyword does more than just "RESET" without operands.
It is (and I think always was) a handy way of resetting, well, everything, without having to name each bit individually. If "RESET ALL" must exclude anything, then exclude RETRIEVE because that's a separate "concept" to Resetting various line characteristics.
|
|
|
|
Post by George on Jul 5, 2021 9:01:52 GMT -5
Guys: I'll go back in, RESET was 'played with' and it seems to have been mucked up - Sigh! Leave it with me. George [UPDATE] OK, the RESET Oops! has been corrected. Here's what I'd like to roll out as the next release. SPFLite26.exe (562 KB) [\UPDATE] |
|
|
|
Post by George on Jul 5, 2021 11:19:54 GMT -5
OK, the release I just pushed out has RESET corrected to be back to what it has been in prior releases. ALL is handled as follows: If the command is simply RESET - Request = ALL - RETRIEVE - LABEL - TAG - COMMAND
- if OPTIONS Reset User is not selected, then USER is also removed
If the command is RESET ALL Any other form of RESET with operands, the ALL is ignored. RESET STATE also adds LABEL TAG and EXCLUDED It looks like the Doc. needs to be updated to include COMMAND along with RETRIEVE, LABEL and TAG. George |
|
