8 replies to this topic

[connor.clark]

There is now a plugin for the VS Code editor: https://marketplace....amcl.zquest-lsp

Basic features it supports currently:

* Underline warnings/errors from the compiler, directly in the editor

* Syntax highlighting

* (very experimental) code formatting, if you have clang-format installed.

 

Here is an example: https://imgur.com/Rz4fAa3

 

 

In the future, we'll possibly add things like contextual autocompletion, and shortcuts for Test Mode / launching ZQ.

[Twilight Knight]

Amazing! I'll try it out soon

This was still on my TODO list, but you beat me to the punch :-)

[Matthew]

This is wonderful to see. Now, we just need to train GitHub copilot on the entire script database and start AI-generating scripting away.

[connor.clark]

This just got a big update for 3.0 ZC: https://zquestclassi...-code-extension

 

I'll be implementing more of VS Code's language server features. If anyone would enjoy a particular feature, let me know: https://code.visuals...eatures-listing

 

Currently I'm working on getting all internal functions (global functions, Game->/Screen->/bitmap-> etc. methods/properties) to provide a documentation comment when hovering over them (currently only have that working for stuff you define in a script yourself).

[Jambu]

Hey Connor thought I would check this out and I am curious how do I prevent VSCode from marking functions from the std library as errors.

[Emily]

Hey Connor thought I would check this out and I am curious how do I prevent VSCode from marking functions from the std library as errors.

You need to set up the extension so it understands what files to look at. In the extension settings, there is a setting for `Default Include Files`. You'll want to make sure one of these is the `std.zh` file.

 

Additionally, if you have multiple script files of your own, they may mark *each other* as errors because they don't know about each other. This can be handled by having a "project entry point" file - a single file, that has nothing in it but #includes to your other files. If you then set THIS file as a `Default Include File`, it will know how to read all of your script files when checking for validity.

[Jambu]

You need to set up the extension so it understands what files to look at. In the extension settings, there is a setting for `Default Include Files`. You'll want to make sure one of these is the `std.zh` file.

 

Additionally, if you have multiple script files of your own, they may mark *each other* as errors because they don't know about each other. This can be handled by having a "project entry point" file - a single file, that has nothing in it but #includes to your other files. If you then set THIS file as a `Default Include File`, it will know how to read all of your script files when checking for validity.

Do you have an example. I have this...

still throwing me errors.

[connor.clark]

I recommend having an include statement at the top of every file that imports whatever the file uses directly. The reason is that the extension only considers each file separately (and anything it includes, recursively) when validating it.

Otherwise, adding all as default included as Emily said is the only other solution.

Your screenshot is not enough information to say anything more.

Currently I'm working on getting all internal functions (global functions, Game->/Screen->/bitmap-> etc. methods/properties) to provide a documentation comment when hovering over them (currently only have that working for stuff you define in a script yourself).

 

(3.0 only) This is implemented now.

 

You can hover over any of the internal functions or global variables to get a documentation comment as a tooltip (if present). You can also Ctrl/Cmd click on these internal symbols to open the relevant "bindings" file, which shows you all the other methods available for that specific internal class.

[Jambu]

I figured it out. I was adding it to the path not as an include file. silly me...