> thought that it works similar to FlashBuilder regarding IntelliSense and the auto additons of "imports".
That is exactly what this feature is supposed to do. An import for a class should be added automatically when you complete it with IntelliSense. If that's not working consistently, please file a bug report on Github with a test case that will reproduce the issue. > Goto does not work properly. One thing worth mentioning is that you cannot go to classes that come from SWC files (including framework classes in the SDK). Sometimes, SWC files include the original source path, but I've noticed that it's almost always missing, so I haven't added code to resolve that. If a class is on the source-path, it should resolve for goto definition. - Josh On Feb 16, 2017 3:55 AM, "OK" <p...@olafkrueger.net> wrote: Hi, I wonder if I'm doing something wrong or if I'm gettting something wrong. I've read the feature list and the ChangeLog [1] of the NextGenAS Extension and thought that it works similar to FlashBuilder regarding IntelliSense and the auto additons of "imports". But for me it seems that IntelliSense and Goto does not work properly. Sporadically sometimes it works and sometimes not... I have to test it a bit more to get some more details. Moreover it seems to me that it never adds the imports automatically. I'm able to compile all the AS3/mxml stuff sucessfully and the compiled test apps works like a charme but at the same time VSCode doesn't recognize some classes or components. Do I miss something? Thanks, Olaf [1] "IntelliSense completion of classes in ActionScript and <fx:Script> blocks now automatically adds imports. IntelliSense completion of classes in MXML now automatically adds xmlns declarations." -- View this message in context: http://apache-flex- development.2333347.n4.nabble.com/VSCode-NextGenAS-Issues- with-IntelliSense-Goto-Definition-Ctrl-Click-and-auto-imports-tp59541.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
