Visual Studio Code (vscode) for QuickApp development

[jgab 2,055]

1 minute ago, Joep said:

I programmed past 2 evenings with this VScode setup and uploading code to my HC3 and it works like a charm. Two things I found out:

 

1. If I use a multi-root workspace then the lsp / intellisense is not working correctly. Like fibaro.getValue doesn't pop up the inline code example. Also the Quick App functions (crawled from the fibemu files, I think) are not always suggested. If I work from the fibemu folder (say fibemu/dev/main.lua) everything works. I think this is a VScode thing, but I can't find a setting to fix this.

 

2. If I start debugging (F5) from a secondary file (not main.lua) the emulator starts but the QA does nothing. Very strange. I stays at running main:

 

Please login or register to see this attachment.

 

Nothing to worry about, I now symlink my second repository to fibemu/dev, but I wanted to notice this.

Yes, the first "bug" I think is vscode or the lua language server.

 

The second issue is that the emulator/fibemu starts to run your secondary file thinking it is the main, and usually there are just definitions and no actions... no QuickApp:onInit() to run etc. So it kind of looks like nothing happens in many cases...

The emulator can be used to run non QuickApp code too (with all the QuickApp functions) and I use that a lot so I don't want to print some warning message either...

What would be nice if there was some vscode setting that to point at the active file when running debug (like in ZeroBrane) so it always started to debug that file and not the one currently opened.

[Joep 195]

On 10/21/2024 at 10:18 AM, jgab said:

The emulator can be used to run non QuickApp code too (with all the QuickApp functions) and I use that a lot so I don't want to print some warning message either...

What would be nice if there was some vscode setting that to point at the active file when running debug (like in ZeroBrane) so it always started to debug that file and not the one currently opened.

 

I tested by changing the launch.json task parameter from ${relativeFile} to ${relativeFileDirname}/main.lua. This works for me.  Now it always launches the main.lua file when also edditing other files with a more complex QA.

 

[jgab 2,055]

On 10/22/2024 at 11:06 AM, Joep said:

 

I tested by changing the launch.json task parameter from ${relativeFile} to ${relativeFileDirname}/main.lua. This works for me.  Now it always launches the main.lua file when also edditing other files with a more complex QA.

 

Yes, but it would be nice to mark the current file in the UI and not need to change launch.json file.

I usually run several "main"s, not named "main", while developing and having to edit a file to point to different places is too much work... However, if you have one focused project it can be worth it.

[jgab 2,055]

Ok, I updated a number of python libraries in requirements.txt - recommend that all users (MacOS or Windows) to redo pip install...