|
|
Post by George on May 21, 2015 19:31:53 GMT -5
Robert: The first error looks like it will be an early reset of the color reset parameters after the 1st change and it not being retained for the subsequent ALL iteration. Haven't looked, this is purely speculation.
The 2nd is, I bet, a result of the new command line keyword hi-lighting option. I'll bet if you turn that off, it will work fine. If true, this might be a nasty one to fix.
All something to be looked at - tomorrow.
George
|
|
|
|
Post by George on May 22, 2015 12:18:08 GMT -5
Robert: Under Options => Screen => Hi-Lite Cmd line Keywords.
(How soon we forget)
George
|
|
|
|
Post by George on May 22, 2015 13:12:14 GMT -5
Robert: OK, I've corrected the first problem with the change command. When an existing CLR line 'goes blank', it was not being stored since the logic says if there is no color attributes for a line, don't waste space saving a blank string. Of course it ignored the fact that there already WAS a CLR line with data in it. Old code from the days before CHANGE could remove as well as add colors. Now to tackle the other one. George OK, 2nd one found. Really dumb one, the flag that remembers whether a marked area has been drawn, was being set at the end of the draw routine - to OFF !! Not ON. Sometimes I truly wonder how I create this stuff. www.SPFLite.com/Files/SPFLite825142.EX_ Just rename to SPFLite.EXE and swap into the normal install folder. George |
|
|
|
Post by George on May 23, 2015 12:15:05 GMT -5
Robert: Was't able to see the Home twice happen at all, but the other part seems now to be gone after I did a bit of tidying up in the handling of the mark line code.
I'll post a new version later after I look at some of the other posts.
George
|
|
