|
Post by George on Jan 16, 2024 10:30:48 GMT -5
Robert: Don't think you saw my email. Can you send me your KLD.AUTO file?
George
|
|
|
Post by Robert on Jan 16, 2024 12:33:18 GMT -5
I was out grocery shopping, just got back. It's 10F here (about -12C), not much fun for going out.
R
We're not quite that bad, it's -7C (about 19F) and sunny.
G.
|
|
|
Post by George on Jan 16, 2024 13:58:21 GMT -5
Robert: OK, your corrupted UNDO filename messages were caused by TWO separate errors, One in CLIP and one in COPY. No wonder the FCLIP macro was hit so badly, it uses both commands.
Hopefully this does it. Please don't come back and say "Nope! Still happening."
George
|
|
|
Post by Robert on Jan 16, 2024 14:10:10 GMT -5
George, I will test this ASAP. I was just wondering, could all the UNDO issues have been prevented if you forced all profiles to have a minimum UNDO level of 1, even if they say 0 ?
Maybe even support a larger default UNDO level? What does it buy the user to have no UNDO level? Is there any advantage to it?
R
|
|
|
Post by Robert on Jan 16, 2024 14:19:00 GMT -5
YAY !!!
Everything works, NO ERRORS !
Whew.
R
|
|
|
Post by George on Jan 16, 2024 15:33:52 GMT -5
Robert: A minimum SETUNDO wouldn't help, the problem was simply oversight in missing the call to the UNDO initializer. Basically, if all the profiles used had the same # of undos - no problem.
It occurs when a session does something which CHANGES the SETUNDO value, and the routine which changed the value didn't call the initializer. We end up with a condition where it seems the # is 25, but it was only initialized as 10. BOOM.
This whole thing has been quite a debugging exercise. You may send the Champagne at your leisure.
George
|
|
|
Post by Robert on Jan 16, 2024 16:37:22 GMT -5
I believe there would be legal impediments for me to order alcohol across an international border. But I will send some virtually via good wishes.
R
|
|
|
Post by Robert on Jan 17, 2024 12:11:14 GMT -5
George: "Basically, if all the profiles used had the same # of undos - no problem."
That suggests that maybe the number of UNDO levels ought to be a global option value, and not something that is specified in a Profile. That way, the number of levels would have to match.
Thoughts?
R
|
|
|
Post by George on Jan 17, 2024 14:33:22 GMT -5
Robert: Yes, that's a 'maybe'. Remember each UNDO level creates 4 files in the \TEMP folder. If you have SETUNDO 25, that's 100 files per tab, and I've seen MUEH screen snapshots with literally dozens of open tabs.
Nothing says that's a problem, SPFLite deletes them all, and even has a cleanup routine that cleans up from any accidental 'remains' - like a crash.
But it would have prevented this last problem from occurring.
George
|
|
|
Post by Robert on Jan 18, 2024 9:44:07 GMT -5
Not to push on this concept, but IF you had an inkling of trying it, one way could be to do a scan of all the profiles, and set a (hidden) global UNDO level to the maximum of any Profile entry. So, if one had 10 and the rest had 5, everything would be treated as 10. It wouldn't require any UI interface changes to do it.
R
|
|
|
Post by George on Jan 18, 2024 11:50:44 GMT -5
I think we need some use feedback here. I'll open a thread asking for comments.
George
|
|