AS 2.0 problem
Out of context: Reply #3
- Started
- Last post
- 3 Responses
- mikotondria30
This was what aged me 10 years doing any sizable Flash project - the unpredictability of finding solutions to problems like that that meant completion dates for deadlines became more inaccurate the closer they got. 2 days to solve this ? No one can afford that - the saving grace of Flash is that there's always another way to do things. Rather than spending 2 days trying to match your concept of incrementation to that of the code you wrote to do it, and giving yourself a minor stroke and putting the project back 2 days, redo it another way. Of the top of my head - have a timeline along which you progress with the as controlling specifically which MC to addtostage, scroll out or in, and eventually removefromstage. It might seem long-hand, and a bit of a hack, but it'll work and when you come back to it in 6 months it'll be easy to understand and you won't have to relearn all the code you spent 2 days learning, that you'll forget in a weeks' time. It fits the mantra of keeping it simple and reducing code and keyframes and actions and all to try it the proper way as you have been doing, but if you haven't nailed something like that within an hour, trash it and do it quick and dirty - you don't get extra marks for being clever. Bosh it out, spend that extra time you save sprucing up the other stuff so the client loves it.