well, in my case I could afford to set listeners to parent container, such as key events. so when I do generate children away projects the constructor were like this new AwayChild(main.stage); then in AwayChild I normally set the listeners but to main.stage I receive instead of its own. Again, is ok up to set to own stage up to level 2 deep, after that I use this trick and all my AIR blues are gone.
> isnt stage the same for all components ? are you new to Flash and all its dark secrets? :)) Fabrice On Apr 15, 2010, at 3:50 PM, webattitude wrote: > How did you fix exactly ? isnt stage the same for all components ? > > --- > thomas > > On 12 avr, 13:53, Fabrice3D <[email protected]> wrote: >> I've noticed strange behavior in 1.5 as well, may be not related depending >> on your project setup. >> >> on my side comparable behavior was related to stage prop. >> >> app --> addChild some awayscene class set some stage listeners--> works no >> errors, rotations etc... >> in one project I saw that when app --> loads & addChild external swf with >> --> addChild some awayscene class, set some stage listeners--> no errors, >> but rotations, visible props etc... are failing >> in my case I've fixed by passing parent stage to child. >> >> I'm gonna move soon over to 2.0. So may be I'll know more by then. >> >> Please keep sharing your findings/tips/blues on the Air side as it will grow >> in popularity with the android capabilities... >> >> Fabrice >> >> On Apr 12, 2010, at 1:27 PM, webattitude wrote: >> >> >> >>> Hello, >> >>> I've made an AIR2b2 app with flex4 and away3d 3.4.2. The app runs fine >>> with linux or vista but is completely erratic with 7 and a >>> touchscreen : some 3d objects stops rotating, renderings seem to be >>> incomplete... >>> any suggestion ? >> >>> have a good day, >>> thomas parquier >> >>> -- >>> To unsubscribe, reply using "remove me" as the subject.
