[wopox3]

Originally Posted by voed Can we disable this messages? Its using so much space. Thank you.

I support. On a small screen, lines take up a lot of space. Please add an option to disable superfluous compiler output text.

[kristi]

Originally Posted by KliPPy Checks if included files are valid, provides links to the AMXX Web API reference:

Can you make it so it only opens the include file in a new tab?

And maybe Ctrl + Click Ctrl + Left Click

[klippy]

Originally Posted by kristi Can you make it so it only opens the include file in a new tab?

You can press F12 or Right Click the link then select Go to Definition, but in the new update there will also be an option to disable links to the web API reference.

Originally Posted by kristi And maybe Ctrl + Click Ctrl + Left Click

There's no way to change that and it's not my doing, it's a part of VSCode's UI. You may go to VSCode GitHub and propose the change.

[klippy]

An update has been published.

## [Version 0.4.0] - 2017-08-29
### Added
- Suggestions/completions for variables and constants
- Some diagnostics for variable/constant definitions
- `amxxpawn.compiler.showInfoMessages` setting - whether compile process shows additional information (arguments, exit code...)

### Fixed
- `[]` and `()` pairs now highlighted too (only `{}` pairs were before)
- CWD is now set to amxxpc's directory when running it

[wopox3]

With the syntax highlighting on STATUSICON_HIDE something is not right

[klippy]

STATUSICON_HIDE is fine, STATUSICON_SHOW isn't. It's because highlight is picking up "STATUSICON_SHOW :" as a tag. There's really no reliable way to match Pawn tags with regex only, and language server protocol doesn't allow me to dynamically add decorations to code.
As far as I've seen no other editor provided highlight for tags and I see why - the syntax is so stupid it's not possible (at least not reliably). Do I leave it as it is or just remove highlight for tags completely?

[voed]

I have some suggestions, if its possible, of course:
1. For functions that have arguments, show hint with arguments by clicking on function name:

• click here:
  
• show this:
  

2. Add open parenthesis automatically when autocompleting function name; if function has no arguments, add closing parenthesis too:

• type "read_fl", click enter, have "read_flags("
• type "client_put", click enter, have "client_putinserver()"

3. Show define value when hover on its name

4. May be pointless as hard to implement, but anyway. Show lang file string value on hover by lang key:

[voed]

Originally Posted by KliPPy Do I leave it as it is or just remove highlight for tags completely?

Maybe just keep highlighting for already existing tags : Float:, bool:, Array:, any:, etc

[wopox3]

So in Ternary Boolean you need to remove the syntax highlighting.
Or find a competent way to determine the ternary operation and the declared type inside it.

[klippy]

Originally Posted by voed I have some suggestions, if its possible, of course: 1. For functions that have arguments, show hint with arguments by clicking on function name: click here: show this:

That's planned. Will probably do it in near future.

Originally Posted by voed 2. Add open parenthesis automatically when autocompleting function name; if function has no arguments, add closing parenthesis too: type "read_fl", click enter, have "read_flags(" type "client_put", click enter, have "client_putinserver()"

That seems good to me, will do it.

Originally Posted by voed 3. Show define value when hover on its name

The parser still doesn't parse #define statements, but it's on TODO. Didn't plan for that hovering thing, but it seems good as well, will try to do it in the future.

Originally Posted by voed 4. May be pointless as hard to implement, but anyway. Show lang file string value on hover by lang key:

I'm not sure, may be pointless. If I ever get to implementing that it will be far down the line, seems kind of irrelevant compared to other features that should get implemented first.

Originally Posted by voed Maybe just keep highlighting for already existing tags : Float:, bool:, Array:, any:, etc

Yeah I thought about that too. That would probably be the best thing to do.


Thanks for your input. Have some

Originally Posted by wopox3 So in Ternary Boolean you need to remove the syntax highlighting. Or find a competent way to determine the ternary operation and the declared type inside it.

I honestly don't think Regex can do that reliably, as I've said. Maybe though. I'll take a look at amxxpc code and try to figure out how it determines which ':' is for tags and which for ternary operator, may help me.