...whether 'tis nobler in the eyes of the user to have a current index,
or to ignore updating as way to save resources and speed up processes...
However, anyone who has 800 messages in the INbox is not a user! That
person is an abuser, far worse than I who have more sorting folders than
can be seen on two screens -- far worse than I who have close to 300
messeages in the SENT area waiting to be culled and/or moved.
On Sat, 10 Nov 2001 03:19:47 -0400, Clarence Verge wrote:
> If I hit "I" (after creating an index), a new index is NEVER created.
Of course not! "I" is a core.exe hotkey; like all the hot keys
dealing with displays, if there is the correct page in cache it will not
be recreated unless you specifically ask for it with "R" ... at which
point a new "look see" will be done, and the old htm overwritten.
> If I select a message and view it, thereby getting an "INDEX" button,
> and hit that button, a new index is ALWAYS created.
This makes good sense. If you are in the process of reading mail,
that would *normally* imply that you have read & trashed other mail and
the index in cache is no longer accurate. One selects INDEX *normally*
if a search for the same thread or a previous message or a message not
yet found in reading is sought; having an accurate Index file is the
only thing which would make the foregoing possible.
But core.exe has nothing to do with it. InSight builds the new
index page and places it in the cache for core.exe to find and display.
You're complaining about what I was finally glad to see. It was
constantly frustrating to go back to the Inbox Index to look for a
specific message, and select a message in the Index only to get an
error screen for "could not load" because that message was already in
trash.
> If instead I had hit "I" there will be no new index.
That is because "I" is a global hotkey, that cares not whether you
are reading mail or writing mail or surfing the web or anything else;
the rule remains the same: If there is an appropriate file in the
cache, a new one will not be created until/unless you use the "R"
hotkey.
> If instead I hit "ESC" (for back) SOMETIMES a new index is created.
And sometimes you end up with an error message if the previous
e-mail file has been sent to the trash bin. It all depends upon where
you are when you go "back," and what you have been doing.
If you have opened the InBox, selected and read mail, not deleted
any mail so you *can* just keep backing up without an error message,
then you should eventually be back at the index. It should not rewrite
at that point because you've left InSight and are back in Core.exe land
with an index page in the cache.
If you have opened the InBox, selected and read mail, followed a
link to a site, and cleared cache at any point, and then ESC back thru
the original messages (which will take awhile since they have to be
regenerated, since they are no longer in cache) and eventually get back
to Inbox index, it will be recreated by core.exe because it no longer
exists after the cache is cleared during your travels.
> Seems to me the cache is just as full in all the above conditions. ;-)
Remember that the cache cannot get "full" past a point. If you've
read a lot of mail or visited a couple of graphics intensive links from
e-mail you received, you may well have been exposed to in excess of 254
tings that require storing in cache. If *that* is the case, the cache
starts clearing itself using FIFO (first in first out) and the inbox
index will get flushed. When that happens, the next return to the index
-- whether by somehow managing to back up, or by using the "I" hotkey --
will require that a new index be created.
BTW, anyone wanting to complain about Arachne cache clearing itself
"on the run" should have to sit and wait for Netscape to suddenly
realize that it has to clear 1,000 files from cache right in the middle
of you downloading a page. <G>
> Also seems to me that core is the thing interpreting both hotkey "I"
> and the button argument file://inbox.dgi. Seems they do not resolve
> to the same thing. i.e. ok, Insight re-creates the index when core
> exercises the line in mime.cfg. That's fair.
> But shouldn't core check to see if the index exists first ?
> It seems do that on the "I" hotkey. :)
Struggle through what I wrote up above, if you can. Simply because you
see "file://indox.dgi" appear on the URL line after doing something in
InSight does *NOT* mean that is all that has been done. InSight can
create a new index file, place it in cache, and have it waiting for
core.exe to find there when inbox.dgi is actually executed. In that
case core.exe does check the cache, and uses the *new* index that is in
there. It just *LOOKS* like core.exe is behaving differently, because
you can't see everything that is being done by which modules when.
WARNING: Every word written by me above could be absolutely positively
wrong, totally inaccurate, and laughingly ignorant. But that's what I
understand after a few weeks (400 or so??) of struggling to gain an
understanding of Arachne.
l.d.
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
