Philphilo wrote:If you want to upload the xml somewhere and pm me a link I will run it in debug mode and see if I can see what is going on.
It will either be it is remembering the value and the function to change it is not working or as you suspect it is caching the function.
I had a quick look at the code but there was nothing obvious.
If you check your private messages, I've uploaded the script I was working on with an explanation of how to observe the issue.
But since I sent you that I tried setting all my "exit" functions to null in order to undefine them when I switch page, like this:
Code: Select all
function phaseNextPage() { jscriptLog("---- TRACE: phaseNextPage"); if (typeof exitNextPage === 'function') { var strNextPage = exitNextPage(); } else { var strNextPage = nextPageNumber(); }; overRide.setDelay(strNextPage,0,"","hidden","","",""); exitGuessCorrect = null; exitGuessIncorrect = null; exitPageInitialise = null; exitActivity = null; exitPromptForSpeed = null; exitPromptForGuess = null; exitPoseQuestion = null; exitNextPage = null; } The way my rather linear script works, that code happens to be convenient because I can put it in one place and it'll work for all pages. But for other teases with multiple code branches, delays and buttons taking you to various pages, it would become a nightmare to code round this issue as I have done above.
I think the cause is the Mozilla engine caching Javascript functions. It does look like there might be a way to turn off the caching (see the link I sent you in the PM), but I'm not sure how you do that at the programmatic level in your GuideMe code. The Mozilla JS caching isn't really needed for GuideMe because all the guide script gets loaded fully into memory anyway. So if it can be turned off, I think it's safe to do so.
Cheers
meson1.




