HISTORY.TXT (for DosLynx v0.43b, June 2012) by Fred C. Macall Introduction In this document, I'll try to take up where I left off in the last history.txt and not rehash the history of the previous versions. Also, I'll try not to repeat the issues discussion presented in the info.htm (or, Quick Start) document included in this release. However, there is a cumulative list of unresolved bugs, issues, and To Do(s) at the end. If you want to know everything else there is to know about my previous releases of DosLynx, you can get that history from: http://users.ohiohills.com/fmacall/dlx2xdoc.zip http://users.ohiohills.com/fmacall/dlx3xdoc.zip http://users.ohiohills.com/fmacall/dlx41/info.htm and http://users.ohiohills.com/fmacall/dlx41/history.txt dlx2xdoc.zip collects the info.htm and history.txt documents for all eight of my DosLynx v0.2xb releases. dlx3xdoc.zip does likewise for all nine of my DosLynx v0.3xb releases. TURLView::setTApsx( ) Revisited TURLView::setTApsx(const char * fragment), in TURLVI39.CPP, was introduced in DosLynx in version 0.26b. And, described in that release's history.txt document. It is where DosLynx goes to locate a #fragment-named label in the TNSCollection of a document's anchors. 'setTApsx( ) expects its callers to supply it with a pointer to the # delimited and null terminated tail of a URL. It assumed that always would suffice to define a fragment. However, when a