At 12:51 02/12/2000 -0500, Marshall wrote:
> > >Why do simple image rollovers cause the processor to work overtime?
> > >If you go to my companies site http://www.cyberworldcorp.com and go
> > >through the splash screen, you'll see some buttons in the upper right
> > >beside the flash. Watch your processor when you roll over them.
> > >
> > >On my win2k machine at work if I move the mouse back and forth quickly,
> > >I can quite easily make it hit 100% usage (Yesterday nights build).
> > >
> > >What is causing this? We're not using :hover so I don't think it can be
> > >anything related to that bug which I know existed (it may still exist,
> > >dunno)
> >
> > If you view the source you might see that your MM_swapimage()
> > MM_preloadimage() etc functions are repeated over and over and over and
> over.
> >
> > I've had problems with rollover and MM_swapimage() type functions
> > before. I counselled a much simpler method of rollover images using the
> > names of the graphic files to select the image, ie corenameOn corenameOff,
> > it saves all that tedious mucking about with arrays (where the problem is).
>
>That still doesn't explain why mozilla uses 100% of the processor when
>the highest I could get Nav4 was 60% by rolling over the buttons like
>crazy. So the code is bad, it's generated by the most popular gui html
>editor out there. There are a lot of other sites which use the same
>code.
Yes I know, its still bad though. And yes it is a bug.
>(I didn't make the page... it was someone else in the company and I
>don't have control over the code)
Can you suggest using a simpler method though?
Simon
