1 person found this helpful
Any errors? Have you introspected the SWC via Flash Builder?
Take a look at the following thread if you havent already, I hope that helps.
i looked at the thread
if i unzip the swc, i do see this content- <versions><swc version="1.0" /><flash version="9.0" build="r494" platform="WIN" /></versions>- <features><feature-script-deps /><feature-files /></features>- <libraries>- <library path="library.swf"><script name="Board" mod="1287606921960" /><script name="NeedHelpBtn" mod="1287606921960" /><script name="WoodTexture" mod="1287606921960" /></library></libraries><files /></swc>but in the package explorer, there is nothing if i try to expand it, although other libs i can expand
Restart Flash Builder and then do a clean.
Or clean and then restart.
If that doesn't solve the issue, remove the referenced SWC and add it back.
Try all 3 in different order if issue still exists. Tell us what happens.
The "Generate accessible SWF file" option had been checked off, any other swc i'd bring in didn't work
checked the option, and finally can see the content of my swc
thanks for the help!
Hmm!? That's good you found yourself a solution, but I am not sure why that option would matter. At any rate, enabling or disabling that option changes the project's actionScriptProperties file. Specifically the generateAccessible property. But I'm thinking it might have refreshed that file, which in turned updated the SWC references. I am not completely familiar with that option, so I may be overlooking something.
If you're willing, can you uncheck that option again, and see if you still have access to those SWCs? Thanks.
Thanks, for posting your solution too.
I unchecked and it still worked, must have been a refresher of actionscript properties, the problem did come back briefly this morning, i deleted the swc and recompiled. I'm starting to think corruption of files might be a problem, although my computer was reformatted last week
Ah, yeah. I had similar problems with FB losing access to SWCs at times. If I recall correctly, it was always rectified by doing one or all of those 3 steps I mentioned previously. Well, at least now we have armed ourselves with solutions for this problem.