I created two flash areas in a site design and find that when I rollover the bottons, (not flash) they effect the performance of the flash motion. I have no idea why this is but really must understand a way around this.
the files are very small, and have no reason to run poorly, does anyone have any ideas on this matter.
Yeah, I don’t really know what the problem would be. I know that OSX and Safari in particular do funny things with SWFs when they don’t think they have focus (it seems like they get extremely low priority in the processor’s stack)… Anyway, yeah, if there’s a lot of animation, or maybe a loop that’s going off ad infinitam or something you would have some noticeable slowdown.
My instinct tells me that it’s a combination of the masking and alpha blending you’re doing on the lower left animation, combined with the browser processing the mouseover code for the rollovers, and if you’re doing the “bouncing” text effect via actionscript, that’s probably adding to the bogging of your system as well.
With that said, it doesn’t look THAT slow on my PC or my Mac… I do see what you’re talking about, but it doesn’t really detract from the site unless you’re REALLY looking for it.
The bounce is just simply motion tween, but I guess I will have to live with it, if there is no alternative. Thanks for your help, maybe I am being to picky but it would be good to know the problem, as I dont see why it should happen, even without the other flash effect it still causes problems
Hi digital, this is crazy stuff. I just created some stupid flash file in a second, placed it in the html and tried again and dispite the really sad file being all of simple text moving up and down it still does not work. ahhhhh can you please help me figure this out D
Hm… yeah, I just looked at your .JS file. I think you’ve over engineered your rollovers. All of that recursive looping through document elements is DEFININITELY causing your problems.
Is there any reason you need such complex scripting just for rollovers?
Yeah, from looking at the JS file some more, it appears rolling over your buttons is creating a HUGE call stack. Every single time you roll over a button you are calling MM_findObj(), which in turn calls itself within a loop ( which will in turn call itself within a loop inside of that call, which will in turn call itself within a loop… etc etc )