I think someone else already posted the answer. The Flash version of the framework classes are different than the Flex version. You need to register the Flex version of the classes into Flash (this is complicated, but see the docs, they're pretty extensive on this).
All SWCs in your libpath (which includes your app directory, by default) are merged together and resolved by versioning. (If you unzip the SWC and look at the catalog.xml file, you can see the version numbers on each definition). If there is a Flash class with a higher version than the Flex class with the same name, you will get the behavior you describe. Best practices is actually to not build the components in Flash, but rather to just build the assets in Flash and export them in a SWC. Then, build the components in Flex and attach the assets to your Flex components using Embed. Cheers, -Roger Roger Gonzalez mailto:[EMAIL PROTECTED] > -----Original Message----- > From: flexcoders@yahoogroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of eerkmans > Sent: Wednesday, April 27, 2005 12:56 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: SWC generates server error > > > > great, thanks a lot ! the error is fixed now. > > Not many people work with SWC components it seems, so if you don't > mind I'm asking you this other question that I have....do you happen > to know why my SWC's screw up my flex interface? I've posted this > problem as well: > > When I place my SWC file in a custom folder instead of right next to > my index.mxml, somehow all kinds of flex properties get overwritten > by the SWC. (also the case with the flex button that generated > the 'name' error) > > For example, I can't use the property 'backgroundcolor' anywhere in > my entire flex app anymore, and borders around containers aren't > shown anymore. > > Also, comboboxes get rendered with strange squares around their round > corners. > > > > --- In flexcoders@yahoogroups.com, "Roger Gonzalez" <[EMAIL PROTECTED]> > wrote: > > > > > > WARNING exporter: cannot export name for init actions > > > __anonymous.0.c:\program > > > files\....\user_components\TfeResetButton .swc > > > > Wow, that's a pretty obscure problem. I wrote the code, and even > I had > > to go dig through the code to see what its doing! > > > > This only gets triggered if the exporter sees an unnamed sprite > with > > init actions (are you using #initclip?) > > > > It temporarily gives the sprite an export name (code dependencies > are > > tracked based on names, so we give the unnamed sprite a unique > handle), > > and then on export it warns you that its stripping out that name. > The > > problem with unnamed sprites is that they don't work with the > normal SWC > > versioning system - if you exported two copies of that SWC and > copied > > them both to your libpath, it wouldn't be able to determine which > was > > the newer version of your symbol, so it would end up including > both. > > > > Coming up with a coherent message to print given that the thing its > > complaining about is an unnamed critter deep in the bowels of a big > > opaque file format is hard, so you got the confusing message that > you > > saw. However, it is only a warning, it shouldn't affect the > behavior of > > your app. > > > > Note that importing code from Flash that uses #initclip is quite > > dangerous in Flex if the code has any class dependencies. We only > track > > class-to-class deps, not codesnippet-to-class deps. > > > > If you want to make the warning go away, make sure that you give > your > > symbols export names. Let me know if you need more details. > > > > -Roger > > > > Roger Gonzalez > > mailto:[EMAIL PROTECTED] > > > > > > > Yahoo! Groups Links > > > > > > > > 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/
