#3 refresh/reload context loss

[Renaud B. Trudel]

The webpart does not currently (v1.3) survive the
following instances, and the context is lost to the default
retraced tree:
- the page is reloaded/refreshed;
- the page is accessed via the back or forward actions;

I have thought up several implementations of how to
solve this, but i've been digging in SvdO's code enough
for this week :)
- the "open" tree branch (number) still appears in the
url -> would a call to the "open branch" function with this
number be possible?
- an ASP variable could be set evrytime a branch is
expanded. Passing a javascript variable's value to an
ASP page is impossible; a workaround would be calling
an ASP page through xmlhttp as such:
// simply "GET" an asp page, so that a particular
variable can be stored in the Session object.
// no other way: passing a value from JavaScript to ASP
is impossible
function setASPSessionVariable(variable, value){
var fileName
= "setSessionVar.asp?" + variable + "=" + value;
var XMLHTTPReq = new
ActiveXObject("MSXML2.XMLHTTP");
XMLHTTPReq.open("GET",
fileName, false);
XMLHTTPReq.setRequestHeader
("Content-Type", "application/x-www-form-urlencoded");
XMLHTTPReq.send();

// alert(XMLHTTPReq.responseText);
}

- using the DDSC.PutSessionState (more efficient than
the above!!) from within util.asp (regardless of whether
the user chooses to enable DDSCEvents or not)
one would have to write a function in the dashboard's
dbview_ie.xsl similar to "function RaiseDDSCEvent".

Are any of these ideas workable?
The PutSessionState option is working for me as of yet
in another webpart (which catches the DDSCRaiseEvent
from MacawJoust WebPart to display the files in the
Category folder selected)
I'll be getting my hands dirty early next week with
modifying SvdO's code to maintain the current context,
and inform him of any solution found :)
Rgds,
/Renaud.