The $T{NEXT,PREV}MSG$ resources move to the next/prev message in a
thread, or to the next/prev thread if at the end of a thread. This is
good. But additionally, our users would find it helpful to be able to
jump from the middle of a thread to the next thread.
I looked briefly at the code and didn't see any obvious way to do this.
Seems like another array of pointers parallel to Index2TLoc etc. would
need to be maintained?
Sort of. You'll need a hash that maps a messages to the first message
of the next thread. The keys would be the index of the message of
interest, and the value would be the index of the first message of the
next thread. Once the hash creation is in place, replace_li_var needs
to be updated to include new resource variables for representing
the next/prev thread.
Note, the computation will add extra overhead since, basically, an
extra pass is needed once thread order is computed to determine
next thread messages.
--ewh
