|
|
Post by MUEH on Jan 13, 2016 12:27:19 GMT -5
Get_LPtr(2) Returns 2 if you have entered cols on data line 1 . It should return 4 as it does when cols is entered on line 2 . here a macro to verify ' MUE.macro
dim liptr as number value 99
liptr = Get_LPtr(2)
Set_msg("M02",liptr, Get_RC , Get_Msg$) Screen Looks like *********top of data ----+----1----+----2 aaaa bbbbb ccccccc no Problem for Data line 1 . Thanks ! |
|
|
|
Post by MUEH on Jan 13, 2016 12:37:56 GMT -5
Tested it in 8.1 8.2 8.3 and Occures in all Versions .
|
|
|
|
Post by MUEH on Jan 13, 2016 16:36:45 GMT -5
Made some more tests if cols is before first data line . x .1 on command line works while x .2 gets no line found error . |
|
|
|
Post by George on Jan 14, 2016 12:05:14 GMT -5
MUEH: Very interesting, you can x out lines 1, 3 and 4, and yet X .2 says not found. Gotta go see how I managed to accomplish this neat feat.
I'll be back.
George
OK, corrected. Boy, this is a very old undetected Oops! type error. Very surprised it has not shown itself previously.
I was just about to start packaging a new release to get the last few bug fixes out, this correction will now be part of that release.
George
|
|
|
|
Post by MUEH on Jan 24, 2016 15:44:23 GMT -5
Installed 8.3.6022 and it solves Problem when cols is first line .
Moved now cols line after last data line or placed MARK command on last line an x .1 or any other x
results in No lines found error .
Tested it with 8.1 8.2 8.3 and it occures in all Versions .
|
|
|
|
Post by George on Jan 24, 2016 16:15:40 GMT -5
MUEH: The fix I put in for your problem has, it turns out, already been reported as causing some other problems. I've corrected it (again), but even my latest version still doesn't like having the MARK line after the last data line, very weird. So there's still something odd going on.
But really, why would you put a mark line after the last line? Or even more so, go to the effort of MOVING a COLS line there where the COLS line command wouldn't normally allow it?
Looks like you're trying to win an award for the most obscure bug possible? ;-))
George
Update:
I've put in a correction for this to handle the condition of special lines immediately preceding the ** End of File ** line. As well I've standardized all the special line inserts to be done ahead of the line they are requested on. So special lines should not occur past the last line any longer.
I have not added any code to prevent users from doing what you did - MOVE a special line to that location. There is no logical need for ever doing this. Many functions in the program reference the last data line and treat it specially. I will not be expending any further effort to cope with what appears to be a conscious effort to break the code.
George
|
|
|
|
Post by MUEH on Mar 22, 2016 3:21:17 GMT -5
Sorry for bothering you again !
Tested it now with 8.4 and all above Problems in Line lookup are solved .
However i found a new one which doesn't occure in 8.3 .
When i moved or copied a COLS line x .second line after new COLS Line Fails with Line not found .
Thanks MUEH
|
|
|
|
Post by George on Mar 22, 2016 12:02:15 GMT -5
MUEH: God only knows how you spotted this one. (e.g. who MOVES a COLS line anyway?)
Fixed it (I hope) for the next release.
George
|
|
