Post by Stefan on Aug 25, 2023 13:43:44 GMT -5
George,
I made a daft mistake.
I used COMPRESS "<a-single-blank>" "<null-string>" ALL command on a file with MINLEN > 0
After a short delay, SPFLite popped up this
Had I not imbibed a Gin and some pre-dinner wine, I might have correctly selected <Save & Terminate> and the following message
would have actually had an <OK> button, instead of an underscore in a blank box (which is what you get if you select <Ignore & Continue>.)
As I said, it's entirely 'user error' that SPFLite crashed (a bit messily or otherwise).
But it does lead me to wonder...
Would it be possible for SPFLite to check MINLEN for a non-zero value, WHEN the <from-str> in a command like COMPRESS or CHANGE is one or more blanks AND the <To-Str> is NULL?
That would avoid the whole issue.
