On 11/25/14, 2:41 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
> >> I’m not sure if the hooks from FB are that low level. I can >> try it myself if you want. Did you make sure that FlexJS and not >>regular >> Flex is compiling the code? Is it using a FlexJS flex-config? Also, >>did >> you restart FB? It can cache SWCs in memory and further complicate >>things. >> > >I managed to fix this problem by removing the framework.swc from the Flex >SDK build path. That is where mx.states.* comes from. I did this for >FlexJSJX, FlexJSUI and MXMLClasses projects. Now there are no such >compile >errors. I am able to resume work on this using FB, so I can live with >this >setup :-) That sounds like the FlexJSJX project is using a regular Flex SDK. The only things in its library path should be playerglobal.swc or airglobal.swc, FlexJSUI.swc and possibly MXMLClasses.swc. Restricting the library-path should also help catch accidental dependencies outside of FlexJS and the runtime. -Alex
