Re: VS Code for i questions

On Thu, 2024-10-17 at 14:34 -0500, DEnglander--- via RPG400-L wrote:

I am attempting to start using Code for i. I was able to download the
software and install it. I have configured it, and can open source
members
and edit them.

I have 3 questions:

2. How do you change the color of the screen? I can change the
themes, but
cannot see how to change much beyond that.

After setting a theme you can control individual settings by pressing
"CTRL ," to bring up the settings (or CTRL SHIFT P and then type "open
settings" and select "open settings UI")

From there click on the level you wish to change

(user/workspace/folder) and then click the puzzle piece (upper right of
the tabs) and open settings json.

The colours of the workbench can be changed by setting various options.

This is what I have (along with lots of other settings specific to the
RISC-V C micro-controller code that I'm currently playing with):

"workbench.colorCustomizations": {
"editor.background": "#0f0f0f",
"sideBar.background": "#0f0f0f",
"activityBar.background": "#0f0f0f",
"editorRuler.foreground": "#ff0000",
"editor.findMatchHighlightBorder": "#ff00007a",
"editor.findMatchBorder": "#00ff0d49",
"editor.findMatchBackground": "#1d6e2f",
"gitlens.trailingLineForegroundColor": "#eb0aff",
"editorCodeLens.foreground": "#eb0aff"
},

"workbench.colorTheme": "Visual Studio Dark - C++",
"workbench.startupEditor": "none",

"debug.console.fontFamily": "Inconsolata, monospace, monospace",
"debug.console.fontSize": 13,
"debug.console.lineHeight": 12.5,


To add a value just add a , on the last line ("#eb0aff") and on the
next line "" and while inside the "" type the name of the element you
wish to change/set... as you type you should see the various elements
that are similar to the name you want... for example:

"editorCodeLens.foreground": "#eb0aff",
"background"

Will show all the elements that are backgrounds that can be changed.

More info can be found at:
https://code.visualstudio.com/docs/getstarted/settings

Its not the most intuitive way of setting some things!

For main settings they can be set in the "settings UI" (which is
searchable) but a lot of the lesser settings have to be done in the
json file. Once you get used to it its not to bad and I guess it cuts
down on the huge coding effort that would be required to allow for
thousands of settings (and for every plug in) on far more detailed
settings screens and means it only requires a parser with validation
for the json file (less duplication of effort) and also means the data
store is always validated (unless opened in say a text editor) so less
chance of corruption.


Hope this helps you get started.