|
Post by Stefan on Dec 19, 2022 5:39:15 GMT -5
George,
Sometimes, the user can enter a valid but perhaps unwise command which takes a long time to complete. Example: Load a large file like _Spflite.bas and issue FIND ALL R'A*' Warning - You'll need to terminate SPFLITE
In this instance, you'll get this pop-up
But SPFLite has not crashed. It is just having to do a lot of work most likely because the user has asked for something inappropriate.
(1) In this situation, a <CANCEL> option that effectively abandons the current command would be ideal.
Any actions accomplished so far are probably reversible via UNDO and there's no need to Crash-Save every open tab with changed data.
In any case, as it stands, the crash-dump is written every time the pop-up occurs.
If the user choses the <YES> reply, it is likely the pop-up may occur several more times, each time with another dump.
(2) Should the Crashdump only be written if the user chooses the <NO> option?
|
|
|
Post by George on Dec 19, 2022 9:32:26 GMT -5
Stefan: Probably.
Also remember if you know you'll be doing a bunch of stuff like that, start SPFLite with the -NOLOOP option, it suppresses loop detection for that session.
It would be nice if the Loop popup could just terminate the last command, but in a single main thread program like SPFLite that's well nigh impossible to do.
George
[UPDATE] Completed. Also fixed a couple of quirks I spotted in there. [/UPDATE]
|
|