> > >Yes, I have been using FB all this while with no issues. But it looks > >like FlexJSUI's mx.states has started deviating from the Flex SDK version. > >Which is manifesting as a problem now. > > In theory it should be ok to deviate from the API surface of the current > Flex SDK.
Of course, it is okay. My point was: it was always pointing to the wrong mx.states package (i.e. the one in the Flex SDK) and since nothing changed in the new mx.states package, this problem was hidden. Now that things started deviating, we hit this problem, which is a good thing. > 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 :-) Yeah, long term, if we can remove all dependencies on the existing Flex SDK, that would be good, especially from an IDE point of view. Thanks, Om
