One thing that I have noticed with existing versions of MHonArc (1.2.x)
is that if you create "Reverse" (ie more recent messages at the top) indexes
then the navigation concepts of "Next" and "Previous" seem backwards. For
example, in a message, if you select the "Next" anchor then you'll actually
get the "Previous" message if you were thinking chronologically. What
"Next" and "Previous" are really referring to are the ordering in the main
index. I know I expected chronological behaviour :-).
What I've done is relabel the navigation components by "customizing"
them. I've appended what I did if anyone else doesn't want to have to think
about it.
I know I'd be interested in having MHonArc "default" to this behaviour in
future versions :-)
Simon.
==============================================================================
<TOPLINKS>
<HR>
$NEXTBUTTON$ $PREVBUTTON$ <A HREF="$IDXFNAME$#$MSGNUM$">[Index]</A>
<A HREF="$TIDXFNAME$#$MSGNUM$">[Thread]</A>
</TOPLINKS>
<BOTLINKS>
<HR>
<UL>
$NEXTLINK$
$PREVLINK$
<LI>Index(es):
<UL>
<LI><A HREF="$IDXFNAME$#$MSGNUM$"><STRONG>Index</STRONG></A></LI>
<LI><A HREF="$TIDXFNAME$#$MSGNUM$"><STRONG>Thread</STRONG></A></LI>
</BOTLINKS>
<PREVBUTTON>
<A HREF="$PREVMSG$">[Next]</A>
</PREVBUTTON>
<PREVLINK>
<LI>Next: <STRONG><A HREF="$PREVMSG$">$PREVSUBJECT$</A></STRONG></LI>
</PREVLINK>
<NEXTBUTTON>
<A HREF="$NEXTMSG$">[Previous]</A>
</NEXTBUTTON>
<NEXTLINK>
<LI>Previous: <STRONG><A HREF="$NEXTMSG$">$NEXTSUBJECT$</A></STRONG></LI>
</NEXTLINK>
