Thanks for the ideas. Our flash dev tried to do something with _lockroot, but that didn't work either. Anyway... I think we are stuck with refactoring...
Kind of weird that there is no good way of getting around this. It would be nice if apps checked to see if there was an existing prototype before they overwrote them. But then again, apps most likely won't work if they don't use their own protoypes. Oh well... thanks for helping... I appreciate the time :) --- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote: > > It doesn't have everything in there, and what is in there has changed > slightly from 1.0 to 1.5. > > I'm with you; that exact reason was given to me when I was using Flash for a > similiar project. This is what happens when you let designers code, but you > have to manage it. > > Couple ideas. > - Try securing the SWF that you are loading. If it's being loaded > insecurely, it may not have access to modify things in the parent swf. End > result; laco can't overrwrite movieclip methods in Flex's SWF because it's a > violation of the security sandbox. Try things like making sure > System.security.allowDomain() in the Flash SWF is hardcoded to some domain > other than where it's at... can't be a sub-domain that differs because Flash > Player 6 would get around it. > - Not sure the internals of Laco, but change MovieClip to the timeline(s) > that it's being used it. For example, if there are classes that are being > used (probably not, hehe) in the designer's FLA, you can pass in that class > reference, thus only affecting it, and not the actual MovieClip itself. > > Sorry bro, I feel your pain. > > ----- Original Message ----- > From: "Bob Remeika" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Monday, October 17, 2005 4:38 PM > Subject: [flexcoders] Re: Movieclip Tweening Prototypes > > > I didn't know that zip file had all of the flex internals stuff. Very > cool. I see that in the source as well, and I'm just trying to think > if there is some other workaround other than ditching laco. The only > reason for the use of laco was for speed of dev for our flash > developer, and the only reason that we are semi-married to now is > because it is used throughout the swf so refactoring is going to take > some time. As usual... our deadline is very tight. :) > > I don't want to change any of the MM source for obvious reasons, and I > don't think it's possible to change the laco source, but even if I > could, it still might not be a great idea. > > Unless you see something I don't, I think we are going to have to > refactor the SWF. Any ideas? > > --- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote: > > > > 2nd project where I've seen collisions with that tween class. > > > > I believe some of the Effect classes extend tween, and some of those > mothods > > overrwrite Tween's, and all those that extend it, at runtime thus > fubarring > > the whole crew. > > > > Why not using the built in tween classes instead of Laco? > > > > ----- Original Message ----- > > From: "Bob Remeika" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Monday, October 17, 2005 3:47 PM > > Subject: [flexcoders] Re: Movieclip Tweening Prototypes > > > > > > This is taken out of the documentation from the extension. Our Flash > > SWF is using lmc_tween.as: > > > > This extension adds tweening methods to MovieClip > > After > > #include "lmc_tween.as" for ActionScript 2.0 (runs fine on Flash > > Player 6) or > > #include "lmc_tween_as1.as" for ActionScript 1.0 > > you can use following methods for MovieClip: > > MovieClip.tween() > > MovieClip.stopTween() > > MovieClip.isTweening() > > MovieClip.getTweens() > > MovieClip.lockTween() > > MovieClip.unlockTween() > > MovieClip.isTweenLocked() > > MovieClip.alphaTo() > > MovieClip.brightnessTo() > > MovieClip.brightOffsetTo() > > MovieClip.colorTo() > > MovieClip.colorTransformTo() > > MovieClip.contrastTo() > > MovieClip.frameTo() > > MovieClip.scaleTo() > > MovieClip.slideTo() > > MovieClip.rotateTo() > > MovieClip.sizeTo() > > MovieClip.pauseTween() > > MovieClip.unpauseTween() > > MovieClip.isTweenPaused() > > MovieClip.stopAllTweens() > > MovieClip.pauseAllTweens() > > MovieClip.unpauseAllTweens() > > MovieClip.ffTween() > > MovieClip.rewTween() > > MovieClip.invertColorTo() > > MovieClip.tintTo() > > > > > > --- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote: > > > > > > There are a bunch of modifications to the MovieClip's prototype in > > the Flex > > > framework. They are too numerous to list here, but most reside in > > > UIObjectExtensions.as and UIComponentExtensions.as. > > > > > > If you can find out what the Flash SWF is extending, and list them, > > maybe we > > > can resolve the issues, and work around them. > > > > > > ----- Original Message ----- > > > From: "Bob Remeika" <[EMAIL PROTECTED]> > > > To: <[email protected]> > > > Sent: Monday, October 17, 2005 2:38 PM > > > Subject: [flexcoders] Movieclip Tweening Prototypes > > > > > > > > > I am sending this out there to see if anybody has built a SWF using > > > the "Movieclip Tweening Prototypes" Flash Extension and loaded that > > > SWF into a flex app. We are currently doing this for a client of ours > > > and we have noticed some issues between the interaction of this > > > extension and flex controls (so far we have only seen the problem with > > > the accordion control, but it may extend to other controls). > > > Basically, the accordion control does not render properly however it > > > will still animate. When we remove the extension from our flash > > > movie, everything works great so we are sure that this is a problem > > > between this extension and flex. We are also using some flex > > > effects... maybe there is a problem with the interaction between the > > > extension, the accordion control, and the flex effects??? > > > > > > Being that I do not have much experience with Flash, I was wondering > > > if anybody has had a problem similar to mine, and if they have a > > > possible workaround that hopefully does not include reworking our > > > flash movie so that it does not use this extension. > > > > > > If I had to guess, the problem stems from the "Movieclip Tweening > > > Prototypes" altering something in _global that Flex needs to animate > > > the accordion control. > > > > > > If anybody has any insight into the internals of flex animation > > > (specifically animation as it pertains to the accordion control) or > > > how to debug the problem further, then your help would be greatly > > > appreciated. > > > > > > Thank you, > > > > > > Bob Remeika > > > > > > > > > > > > > > > > > > > > > -- > > > Flexcoders Mailing List > > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
