Post by Stefan on Apr 3, 2023 3:36:07 GMT -5
George,
First seen in V23086 but also in v23092
There's something fishy with the (Paste) primitive when pasting into the command line.
Only the first copy/paste operation is correct. In subsequent copy/paste operations, blanks replace part of the pasted-string at the end.
The number of blanks changes with each attempt and can be longer than, and thus replace, the whole initial string!
Once this happens, all (Paste) operations to the command line simply look 'blank'.
Take a string in the data like '0F0E011202140615031305'x
1) Mark it with SHIFT+Mouse-drag and hit Ctrl-C .... mapped as (Copy)
2) Move cursor to command line and hit Ctrl-P .... mapped as (Paste)
First time, all is well
Repeat the above
This (and subsequent times) part of end of '0F0E011202140615031305'x will have been replaced by blanks.
If you Mark and (Copy) a different string, part of that will appear corrupted by blanks when you (Paste) it into the command line.
The (Paste) operation is correct when it occurs somewhere in the data portion and not the SPFLite command line. Hence I think(!) (Copy) is blameless and (Paste)+Command Line is the issue.
I also note that if I use Windows' own "Paste" to place the value into another application like Notepad (or this forum), the whole string appears as it should, except that it is followed by a 'newline' even though no 'newline' was marked in the source file.
