Second Thoughts...

[Robert Holmgren]

Michel: For the first time today, playing around with this speller toggle very
intensively (whenever I got bored with editing, which was often), a couple of
times I experienced sudden crash of the PCLEXAM speller (is that "PC LEXicon
AMerican English"?). It just stopped working. Maybe this is the problem that
SysOp was talking about(?). I could restore function by closing the *window*
down (not the whole session), then reopening the document in a new window.
Among the symptoms: "VA/NV UD" suddenly didn't report anything; ®VA$ZZ¯ would
no longer pick up the word at the cursor location, but would instead pick up
the current filename or a random string in the STACK, or whatever -- junk.
Trouble was, it didn't happen often, and I could hardly ever reproduce it.
Finally, I found that I could force it to happen if I opened a long document in
eXPanded mode, jumped down to the end of the document, then tried to toggle
into Draft mode and use the speller. The workaround, which seems good so far,
is to JuMP to TopOfFile, switch on Draft mode, then JuMP back to my original
place at EndOfFile. Anyway, I modified frame {{5goThes}} to take account of
this (plus other refinements), and my setup is working smoothly again. It's
nclosed with this msg.

But it made reminded me that there might be other problems here that I'm not
experiencing -- maybe people who use the Menus intensively find that PCLEXAM
crashes all the time, or maybe it crashes if you do a FIND, or a
seventeen-character Search-and-Replace, or any off-the-wall unpredictable thing
... In short, there could be a lot of seemingly unrelated reasons that it
would crash, having to do with a memory location getting overwritten, or
something like that. Maybe SysOp is basically right (he's *supposed* to be
right, isn't he?), and I just "get away with it" (most of the time) because of
some peculiarity in my setup. It may not be worth investing much effort in; it
eroded my serenity anyway, h?las.

*Enclosed File: GOTHES.FRM