len
Freshman Member
Posts: 15
|
Post by len on Jan 15, 2014 6:16:10 GMT -5
A funny sequence of events puts the cursor in the wrong position. It goes like this: - I repeat a line using the R line command. - I position the cursor on a position in the line I repeated from. - I use ctrl-delete (it is mapped to (eraseEOL)) to erase the end part of the line. - I move the cursor a few lines down and use the R command on that line too to repeat the same procedure on that line. - Now the cursor is positioned at the first deleted character on the line that I repeated in the first place.
This is not a big issue, but I use a sequence like this sometimes when I split a Cobol line in two because a variable name becomes too long to fit before the PIC specification.
|
|
|
Post by Jo on Jan 15, 2014 6:50:57 GMT -5
yes, I've seen it on V6.1, but forgot it. Its just the R linecommand after (EraseEOL).
|
|
|
Post by George on Jan 15, 2014 15:20:42 GMT -5
Len: Jo:
Corrected, it will be in the upcoming 7.1 fix release. This is another example of the difficulty in figuring out where the cursor should go in a program like SPF, where on any Attention type interruption (Enter or Function type key) there may be a whole pile of different routines invoked; different line commands, multiple primary commands etc. each of which, when finished, issues a request to 'put the cursor HERE' based on what they did. There all have to be juggled and prioritized to determine just whose request is to win the 'me first' contest. This was simply a problem where EraseEOL was issuing a request using an incorrect priority.
It would not have been noticed if you'd pressed Enter following the EOL and before the second R request. But why should you?
George
|
|
len
Freshman Member
Posts: 15
|
Post by len on Jan 15, 2014 16:03:00 GMT -5
Thanks a lot! You are marvelous! / len
|
|