[bombingpixels]

Hello,

I have a big mess. I this file: It's Here (FLA) and it's made me completely lost. When you download it, you can clearly see my intentions, I was trying to get each text box to fade out and then another one to fade in when a button was clicked but for some reason the home text box has a little bit to much fun and keeps appearing every third time you click a button, by the way, I haven't set up the last button yet, this would be very helpful if you could show me how to get it to work.

By the way, here is what the final fla currently looks like.
Once again, Cheers for any help,
Jeff

p.s. I love adding the fun smilies

[dan]

Right I've had a quick look, but it's pretty hard to make out. That files a real organisational nightmare. I'm guessing the xml loading is currently redundant?

A lot of the code you've written on the buttons could be executed with a function rather than all of those repeats.


I may have got the wrong end of the stick but from what I can tell the main problem is your approach to the task. The problem seems to be the order your triggering things, but it'll take me a bit to sift through it. Can you not trigger the page change from within your fader movie clip? this would reduce the need for all that code.

Set up two variables, one to track the current page and one to track the next page (last pressed). pass these to a script within the fader that triggers when the fader is at it's darkest. swapping / changing the _visible value of the two clips in question. i.e..

_root [current]._visible = false;
_root [next]._visible = true;

of course you'd have to keep track of the variables and remember to initialise them properly when the movie first starts. Clicking a button simply updates the variables then sets the fader mov off to do it's work. job done.

Incidentally, look at modularising your code more. drop the _roots and use _parent and _this more it makes your code far more portable. ok it might not be important in this example but good practice is good practice and it's harder to unlearn bad habits than to use good ones from the get go... as people say.

Good luck.

PS, if that is a. wrong or b. doesn't help at all - give me a shout

D.

[bombingpixels]

Thats an ingenious idea, that should work perfectly, thank you so much!

[dan]

hang on a mo, is he takin' the piss? I canna tell...

[bombingpixels]

well... what do you mean? I haven't gotten the code yet, but I think it should work, is there a problem with it...

yes... I know I stink at flash

how do I setup _root variables, I'm lost

[dan]

Oops, I just meant the ingenious bit sounded a bit sarky. Anyways, I was obviously wrong and by way of appology I'll work you up a quick example to help you along your way... just give me 15 mins

[bombingpixels]

oh ok, didn't mean to souund that way, I just would have never thought of that and I don't know enough to knwo that that was not a method that would work.

It's all good however, thanks
Jeff

[dan]

Right here you go,

You can view the example here...

http://www.danedgar.co.uk/extras/fad...deExample.html

There's a link to the files there as well. If you have any trouble understanding it, give me a shout.

D.

[bombingpixels]

works very well... my project can continue thank you

[dan]

course it does

glad to help, another dan hit and run...........

[dan]

Originally Posted by bombingpixels

yes... I know I stink at flash

Just as a little extra, sorry if that sounded a bit harsh up there, it wasn't meant to. What you wrote wasn't crap it was just not the best way to go about it. Just trying to give you some pointers about what you might need to look at to get you on the right track. It'll come with a bit of time... good luck on the ol' portfolio project

D.

[bombingpixels]

it's all good, thanks