Have been working on this project for 8 months or so. contains many layers film clips and activities etc.. I have noticed in final testing that if I try to "break" it by rapidy pressing between buttons to load various pages, my Flash starts to play at highly accelerated frame rate.---> One example of this is that I have a button that has a heart monitor type of animation that plays at a heartbeat type of speed.... when it bugs out this is flashing really rapidly and also other movies are running way faster than they are supposed to... This doesnt happen all the time, but is happening and there is no error message in the compiler errors or output to explain what is going on.
Cheers for any help
I was in a similar situation when I had to make a navigation that had a TreeMenu Component, MovieClip buttons and keyboardEvents Listening all the time for user input.
When testing rapdidly and randomly I noticed (since I was dynamically creating objects, tweens etc.) that the application started to act weird, I ended up solving the problem with an InputManager, that was basically nothing else than a Mediator,
that allowed/disallowed Events to be triggered depending on which state the application was in, for example if sth. was tweening on the stage I considered that as a "transient" state during which further User Input was blocked.
If your project has reached a certain complexity its no piece of cake to make that working.
so in a cave man type of way i could put a clear "screen" over all the buttons for a few seconds each time an option is pressed to force the user to wait a while before they can choose anything else... I know that's a pretty dumb idea.... My only concern is that then they think that the fact they cannot press another button for say 2 secs is a bug!
Just to give you an idea, here is what I have been working on for the last 12 months (2 projects)
It really depends on the details, you have to isolate the problem and then aiming for a local Anaesthesia rather then putting your app in an artificial Coma to make the pain go away. If you get the picture
I looked at your project, congrats, you really put a lot of effort in there.
How are you handling the different sections of the app, with scenes? with loaders? Do you use the timeline much etc.? Do you use classes or code on frames? Do you use as2 or as3? Which platform do you target? How do you intend to distribute the work?
These would be all important to know to give you viable options to choose from.
A good read to get introduced in "How to debug without Errors" is here
Look especially at the section within there: Repeated Execution Code
The flickering of some of your buttons in the demofilm, could be caused by this.
Hey thanks for checking it out!
Ok so it is AS3 I use some code on the timeline all the different parts are movieclips and then each of the activities inside is on a keyframe, and do use code on frames but I also have a document class and have navigation and "global" variables all happening from there. The finished product will be distributed... wait for it.... on DVD-rom (ha ha!) Most of the flickering buttons that are on my test film are from where I have sped up the footage.. but yes this is what happens when it bugs out. you really notice it because I have separete sounds that are loaded into a sound channel and I have edited some movieclips to work with the sound.. so when the project bugs out the sound still plays at correct speed but the movieclips are way way too fast.. not too good.
Anyway, this is in hard core me trying to break it mode. I dont really think a "normal" user will be punishing it so ... but i would like to be able to make it bulletproof. In the future I think that my employers are looking to create web based projects so I am hoping to be able to use Flash to create HTML interactive content for someone else to load up in Dreamweaver.