The first thing you’re probably going to notice is the update notification for the rc.2 release:

Vshaxe 2.8.0 also updates the eval debugger introduced in 2.6.0 to be compatible with rc.2 (it’s no longer compatible with rc.1 or earlier!). Thanks to @Simn’s efforts, there have been major improvements to the debugging experience, such as:

“step over” being handled much more smoothly

support for threading

macro entry points in the call stack - for init macros, it shows the --macro argument:

for other macros, the call stack item is even clickable and shows the location of the call:

Another major improvement that’s worth mentioning: parser errors are now shown in diagnostics. Technically this was already part of vshaxe 2.7.0, but required Haxe dev to come into effect.

I can’t count the number of times I’ve hit “compile” only to have the compiler yelling at me about a missing semicolon. With auto-save and diagnostics you easily get into the mind-set of “if nothing is red, it should compile”, but that just wasn’t true for parser errors. No longer!

I have question about “parser errors are now shown in diagnostics” . It’s still need to save ( or set to auto-save) file to show the error , right ? Is it possible to show error without save (similar to Eclipse IDE at example ) ?
Also I tried Quick Fix … ( Ctrl + . ) , but show “No code actions available” . Do you planning to add “Quick Fix…” ?

There’s a number of quick fixes / code actions available, even long before this release. What’s new is support for the new “Auto Fix” command. Are you sure the cursor was in a location where one of these code actions was applicable?