|
Post by Stefan on Apr 17, 2021 3:25:20 GMT -5
Hi George,
I just experienced the new LOOP window....
(I saw half a dozen of these pop-ups because I was executing a CHANGE p'=' ' ' ALL 16 100 on a 40,000 line file. My bad, I meant p'^' instead of p'=' but there you go.)
Confusing I nearly clicked the wrong answer! I think it is confusing because it asks the question from a 'crash' point of view rather than the user's perspective.
You are asking the user to reply YES to TERMINATE and NO to CONTINUE.
From the user's perspective, given a choice, s/he wants to CONTINUE and not TERMINATE.
Suggestion1 : Reverse the question so that "YES" means continue and "NO" means crash/terminate.
Expensive
I also tried it once with a TERMINATE reply. To my surprise, SPFLITE just died.
Why surprise?
Because a bonafide crash (e.g. C0000005) would ask me whether to save my open EDIT sessions or just die.
Hence I expected a non-crash, ie. a LOOP detection to do the same.
Worse still, it did NOT save any open edit session either.
Suggestion2 : Add the capability to save open edit session(s) before Termination, and offer the user a 3 way choice - CONTINUE | TERMINATE with SAVE | TERMINATE no save
|
|
|
Post by George on Apr 17, 2021 14:51:00 GMT -5
Stefan: OK, I reversed the YES/NO.
Also did a major revision to the Crash Save logic and got it to work with a Loop style crash. The problem originally, (and why I gave up last time) was that trying todo a SAVE ended up allowing whatever loop occurred to simply resume, and we ended up back in another loop.
So I had to split the SAVE into a new thread and spawn that off in the crash handler. But then, being a separate thread, many of the routines used by SAVE had to be tweaked to work properly. (addressability problems, like in 360 assembler). But after a few hours of head banging, it seems to work.
George
|
|