You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here an aglomerate of issues related to the settings UI and implementation.
You currently have an array of tools, but only one is selected in the General page. All others should not be shown, and only the configuration for this tool should show up, in the same page, just below the tool selection under a section like "Tool options".
The last point also applies to the linter and formatter settings.
A lot of these options seem completely unrelated:
GTKWave installation directory should probably be in a GTWWave tool page
The waveform viewer selection should come before all gtkwave options
The manual compilation order setting is among those, but has nothing to do. Plus, it seems like something that's more related to a specific tool, although I don't know what it does, and couldn't find documentation for it.
And that's just for 1 page with 6 fields.
All sections wich have a single subsection should be a single page. You should not have to first expand the section, then click on "General"
This one is actually pretty funny:
Actually, all of this is mostly trivial things, but since the documentation is very very sparse, and examples even rarer, it makes up for something that's super hard to work with, although once you get the hang of it, it works incredibly well!
My recommandation may be very radical, but that is how other extensions work, and I think it works very well.
Move all settings related to the user (not to the project) to vscode's own settings mechanism.
All binary paths (python, make, gtkwave, etc)
All preferences (stutter mode, schematic viewer, etc)
Move all tool settings to configuration files. This is often how these tools are configured anyway.
Is there anything remaining?
Overall, thank you for TerosHDL, it works super well, and integrates nicely with VSCode.
Have a good day!
The text was updated successfully, but these errors were encountered:
Here an aglomerate of issues related to the settings UI and implementation.
This one is actually pretty funny:
Actually, all of this is mostly trivial things, but since the documentation is very very sparse, and examples even rarer, it makes up for something that's super hard to work with, although once you get the hang of it, it works incredibly well!
My recommandation may be very radical, but that is how other extensions work, and I think it works very well.
Overall, thank you for TerosHDL, it works super well, and integrates nicely with VSCode.
Have a good day!
The text was updated successfully, but these errors were encountered: