Preserved Topic: Adobe vs. JavaScript Rollover

Does anyone use the PS 6.0 / ImageReady rollover feature as opposed to coding
their own JavaScript? My rollovers have those pesky little "busted link" delays
and I'm looking for solutions - possibly getting my "sugar daddy" employer
to foot the bill for a Juicy upgrade.

BTW-
I may be showing my ignorance (again :-), but is there a way to stop those image rollover delays within JavaScript?

Thanks for any info.

What delays are you talking about? Only thing that comes to my mind is that rollover images aren't preloaded and you have to wait till they are downloaded.

Oh, BTW I write all JS by myself...

I like to steal the roll-over script from handson.nu

click the link at the bottom.

>What delays are you talking about? Only thing that comes to my mind
>is that rollover images aren't preloaded and you have to wait till they are
>downloaded.

well, for instance, I have a nav bar on my site that has this code:

<script><!--



  weblog_rollin=new Image();

  weblog_rollin.src="nav/navbarweblog.jpg";



  nav_rollout=new Image();

  nav_rollout.src="nav/navbardim.jpg";



  function weblog_changein () {document.images[2].src = weblog_rollin.src;}

  function nav_changeout () {document.images[2].src = nav_rollout.src;}

...

...and it changes in via the following:

<area href="http://www.kevincar.net/greymatter/gmindex.htm"

    target="Page_Body" shape="rect" coords="10, 14, 84, 34"

    onMouseOver="weblog_changein()" onMouseOut= "nav_changeout()">

...every once in a while I get a "busted link" notice that goes away after a second -

Max, you mentioned preloading -
I know you're going to become a multi-zillionare soon what with the
pending deal for HTML Beauty, but could you take a moment to
explain this concept a little more fully?

Preloading involves storing the image in the browser cache creating seamless rollovers. Basically it involves creating a new Image Object which you are doing with this code:

weblog_rollin=new Image();
weblog_rollin.src="nav/navbarweblog.jpg";

That right there is the simplest form of preloading. You are creating a new image called weblog_rollin and downloading the image (even if it's not displayed). Then in your over function you substitute the src of one image with the src of this. So even though you aren't aware of it you are actually preloading.

Now what could be happening is for whatever reason the original image is loading first, and before this cached version can load you are mousing over the image before the second one loads into cache. However if you just give the page a sec to fully load (You get the little "done" message) this should not happen also you could put all your preloading in the head so all the images are in cache before it even tries to render the page.

OR

I've noticed that with IE depending on my prefrences if I have my browser set to always check for newer versions (TOOLS>> INTERNET OPTIONS>> TEMPORARY INTERNET FILES >> SETTINGS) of a page that IE will always try to download the image instead of using the cached one. Try setting this to Automatically or Never and see what happens.



Walking the Earth like Kane

[This message has been edited by bitdamaged (edited 05-21-2001).]