[Mistrick]

What about autosave before compilation?

[klippy]

To be honest it should have never been a command, but a build system instead. I'll see what I can do.

[klippy]

Published 0.6.3, but forgot to update the changelog, will do it for the next version.

• Added an icon to the extension, thanks to Adam Richard. You can check it out HERE. If you think you can do a better one send it and I'll take a look. Another customizable element is the dark purple background ("banner") on that page, so suggestions for that are welcome as well.
• Will now automatically switch to AMXXPawn syntax if there's #include <amxmodx> on the first line, in case you open some unknown file format (say .inl).
• Added code regions - code between //#region and //#endregion can be folded.
  

You can also propose any changes (be it the marketplace icon, banner, or anything else) by making a pull request on GitHub

[voed]

Great! What about variables autocomplete and hints?

[klippy]

Originally Posted by voed Great! What about variables autocomplete and hints?

If you mean for local variables then most likely never, or in far far future. That would require a complete rewrite (or else be extremely slow and ugly). To be honest if you keep your functions small and clean you can't really lose track of local variables.

By the way, I've been working hard on creating a regex to match tags properly.
Now it works well in ternary operator expressions, ignores "case" and "default" and works for any tag (not just predefined ones):


Also works properly for tag lists:


I also plan to bring doc-comments on hover and completions, Go to/Peek Definition (already done) and possibly #define completions in the next release.

[voed]

Originally Posted by KliPPy If you mean for local variables

No, i'm about global constants, #define declarations and maybe variables:

VSCode already have constants hover, but without its value

[klippy]

Originally Posted by voed No, i'm about global constants, #define declarations and maybe variables: VSCode already have constants hover, but without its value

It's not actually VSCode's, it's extension's hover. I may be able to do it. It's rather easy for a single declaration on the line, but when there's more than 1 declaration per line it can get difficult to parse (at least with my current parser).

[klippy]

Update 0.7.0 has been published.

## [Version 0.7.0] - 2018-03-01
### Added
- Go to Definition/Peek Definition for functions and global variables
- All tags are now highlighted, not just predefined ones
- Tag lists are now highlighted
- Tag highlighting works properly in ternary operators
- Doc-comments are now displayed on signature help/hover/completions
- Pawndoc grammar - doc-comments are highlighted separately

New sexy doc-comment syntax:


@deprecated is an exception and has its own highlight to stick out:


Doc-comment showing up on hover and Peek Definition:

[HamletEagle]

Can you make it that before the plugin is compiled the sma file is automatically saved? I'm used with that from Arkshine's NP++ and it gets annoying because I have to save manually or I get an amxx file that does not contain the changes I made.

[klippy]

Originally Posted by HamletEagle Can you make it that before the plugin is compiled the sma file is automatically saved? I'm used with that from Arkshine's NP++ and it gets annoying because I have to save manually or I get an amxx file that does not contain the changes I made.

Done, just update. Would've done it last night but Windows update goofed on me hard. Duplicated start menu shortcuts, and even worse, changed some paths in the %PATH% environment variable. Micro$oft please fix.