Hi Josh El mié., 5 dic. 2018 a las 17:59, Josh Tynjala (<[email protected]>) escribió:
> Carlos, can you include more details about your issue? > > > MX RO test with Jewel > > Can you mention the exact project inside royale-asjs that I can load with > VSCode to see this issue? I'm guessing that it might be one of the > RemoteObjectAMFTest projects, but there are more than one! > > Check this one: https://github.com/apache/royale-asjs/blob/develop/examples/mxroyale/RemoteObjectAMFTest/pom.xml but notice that App setup by default is not the right one (check lines 49 and 50 here): https://github.com/apache/royale-asjs/blob/develop/examples/mxroyale/RemoteObjectAMFTest/pom.xml You must use "App_Jewel.mxml" Remember to use "feature/refactor-config-name-changes" branch where my commit is reverted and things are set up like Alex want. You should try to make another config (for example: "jewel-config-template.xml") that can pick up Jewel and MXRoyale SWCs and VSCode and your extension should not show any errors. > > Results: you should see the problems in VSCode > > Can you list the exact problems that you are seeing in VSCode? I'd like to > make sure that I'm not running into unrelated issues. > With Alex changes all classes coming from MXRoyale are not recognized hence show error. If I try to make a new config file and add MXRoyale, rebuild all and SDK too, reopen VSCode, nothing changes So my bet is that there's some issue in Royale that makes this new config changes not work far beyond the special configuration Alex did and need to find where is the issue. Other possibility is that VSCode extension is failing, but since it already loads different configs, this seems more strange to me, although possible. > > I don't think that this is an issue with VSCode or with the changes that > Alex made. I suspect that it's just some configuration changes that are > needed. > > - Josh > Thanks for looking into this Josh -- Carlos Rovira http://about.me/carlosrovira
