I'm not sure that I can help you without being there - that is I think that this is all on an intranet and that I might have to see the setup.
But we might be able to work it out.
First of all, the obvious solution would be, once you see that in the window, click on it to advance the page.
If you don't see that in the window, or clicking on it doesn't advance the page, then we need to setup a list of the pages, probably like what I have in my previous code. Only instead of cycling through them, put up a little pagination thing at the top, above the iframe, where you can click for page 1, page 2, etc.
And have the refresh work off of the current location of the iframe.
BTW - in my previous code I introduced a bustcache variable to add to the query string. That was to ensure that the server would fetch a fresh copy of the page and not allow the browser to show a cached copy. Something similar should probably be done for the pagination links. So something like so:
Code:
<html>
<style type="text/css">
#pagination a {
padding-right: 1em;
}
</style>
<div id="pagination"></div>
<iframe id="if_one" src="" style="width: 2500px;height: 2000px;float: left;margin: 20px;"></iframe>
<script type="text/javascript">
var pages = [
'http://www.dynamicdrive.com/',
'http://www.dynamicdrive.com/forums/forumdisplay.php?2-Dynamic-Drive-scripts-help',
'http://www.bing.com/' //<-- no comma after last page address
], p = pages.length, paginate = document.getElementById('pagination'), thepage;
while(--p > -1){
(function(p){
var a = document.createElement('a');
a.href = pages[p];
a.appendChild(document.createTextNode('Page ' + (p + 1)));
a.onclick = function(){
var bust = this.search? '&' : '?';
bust += 'bustcache=' + new Date().getTime();
window.frames[0].location.href = this.href + bust;
thepage = this;
return false;
};
paginate.insertBefore(a, paginate.firstChild);
pages[p] = a;
})(p);
}
thepage = pages[0];
function loadIframe() {
thepage.onclick.apply(thepage);
setTimeout(loadIframe, 120000);
}
loadIframe();
</script>
</html>
However, it is possible that adding anything to the query string might confuse the server. If so we will get rid of that part and hope for the best. If the pages as served by the server have a no cache header on them, that would probably be all that's needed to prevent a cached version from being shown by the browser, and then the bustcache variable would be superfluous even if it caused no harm.
Java Script for cycling through pages?
Reply With Quote
Bookmarks