There seems nothing wrong with the process you describe. What seems to be the current problem though? Is it that the navigation keeps rebuilding infinitely, or is it when the bg changed the nav crashes as I understood before?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Weyert de Boer Sent: Tuesday, 11 April 2006 10:58 AM To: Flashcoders mailing list Subject: RE: [Flashcoders] > Effects in Flash Hi > > If I understand correctly I think you need an extra mc at the bottom > Prev > background -> navigation -> content > New > timeline -> navigation (depth 2) -> content > > timeline -> background (depth 1) Yes, It might be a good idea to explain to current code base a bit. It's mainly based on "simple" version of the MVC. I happen to have a SiteController, and SiteView class which handle all the stuff of the Flash website. For example, I have a displayBackground()-method in the siteController which triggers a similar method in the siteView-method. I hooked up some addEventListeners to the SiteView instance. It listens to the events: navigationStartEvent, navigationCompleteEvent, backgroundStartEvent, backgroundFadeInitEvent, backgroundCompleteEvent. The events get triggered from the approriate associated movieclips which get created at run-time in the SiteView class. Now when I load the website I construct the SiteModel class, which will load the xml file with the news and other stuff I need. Now when this XML file has been succesfully triggered it will dispatch a event called "dataAvailableEvent". This then triggers the method createBackground: private function createBackground() { trace( "createBackground()" ); background = createBackgroundContainer(); background._x = 0; background._y = 0; siteView.displayBackground( background ); } Now as you might expect the SiteView will do the rest of the job, i.e. attaching the movieclip for animation, and make the empty movieclip for the image. After this animation has been done this also will raise a event called "backgroundCompleteEvent", this again will trigger the createNavigatio-method etc. You get the drill. Once this all is done, the applicationInitiatedEvent will be dispatched this method will then try to find out which page is needed based on the URL. If is not known it will the trigger the "default" button, via: btn_home.onRelease(). This will then load the content, which currently cause a infinite loop ;-) > Function changeBG( bgMC ) { > // unload previous bg > // load new one > } > Yes, but then I would need to make some sort of flag to ignore posting the backgroundComplete-event in the Sitecontroller-instance. Probably it's a easy way to solve this problem, though. Maybe I should just sned some parameters a long with the creaeBackground-methid i.e. AppStart. Maybe I should just sleep over it! Any suggestions are apperciated, maybe my current design sucks. Yours, Weyert de Boer innerfuse* http://www.innerfuse.biz/ _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
