Settings and commands
Open VS Code Settings and search for GPPL, or edit your User Settings JSON. Project-specific overrides can be kept in workspace settings when you intentionally want to share them.
Language and tracing
Section titled “Language and tracing”| Setting | Default | Purpose |
|---|---|---|
gppl.encoding |
windows1252 |
ANSI target for character validation; also synchronizes the GPPL file-encoding preference. |
solidcam-gppl.trace.server |
off |
Language-server protocol tracing: off, messages, or verbose. |
For encoding, the other supported value is windows1251.
The display language follows VS Code. Run Developer: Reload Window after changing it. There is no separate extension-language preference.
Semantic highlighting is enabled for GPPL by default. If colors look incomplete, check the effective editor.semanticHighlighting.enabled value for the GPPL language. The color theme determines the actual colors.
Color theme and highlighting
Section titled “Color theme and highlighting”For all token categories, copyable settings and a step-by-step walkthrough, see Customize highlighting. It covers the categories available in Community 1.7.0, with compatibility notes for 1.6.3.
To select the bundled theme, open the Command Palette (Ctrl+Shift+P), run Preferences: Color Theme, and choose GPPL Classic Dark in version 1.7.0 or later. In earlier versions, choose GPPL UltraEdit. The theme was added in version 1.6.0; the new name keeps the same palette. Selecting it changes the VS Code color theme; it is optional.
The settings ID remains GPPL UltraEdit. Keep "workbench.colorTheme": "GPPL UltraEdit" and [GPPL UltraEdit] blocks in workbench.colorCustomizations, editor.tokenColorCustomizations, and editor.semanticTokenColorCustomizations. Existing selections and overrides continue to work without migration. Use the same ID for new settings JSON entries; GPPL Classic Dark is the display name in the theme picker.
The palette distinguishes procedures, built-in functions, keywords, data types, comments, and strings. Single-quoted literals, commonly used for display formats, are orange; double-quoted text is white. abort, exit, return, and break are emphasized in red, bold italic text. Quote style controls the string color; this does not determine what the string means at runtime.
You can keep your current theme and adjust only GPPL colors in Preferences: Open User Settings (JSON). Merge these rules with any existing editor.semanticTokenColorCustomizations setting:
{ "editor.semanticTokenColorCustomizations": { "rules": { "string:gppl": "#FFFFFF", "string.format:gppl": "#FF8000", "keyword.interrupt:gppl": { "foreground": "#FF0000", "bold": true, "italic": true } } }}The :gppl suffix limits these overrides to GPPL. string.format selects single-quoted literals; keyword.interrupt selects the four control-flow keywords above. Semantic token colors can override syntax-only colors, so use these rules when changing analyzed GPPL text.
PRO indexing
Section titled “PRO indexing”These settings apply to invited testers using the PRO closed beta. They do not enable multi-file analysis in Community.
| Setting | Default | Purpose |
|---|---|---|
solidcam-gppl.workspace.maxFiles |
5000 |
Maximum .gpp files admitted by the workspace scanner. |
solidcam-gppl.workspace.excludeGlobs |
See below | Directories and files excluded from scanning. |
The default exclusion list is:
[ "**/node_modules/**", "**/.git/**", "**/bin/**", "**/obj/**", "**/dist/**", "**/out/**"]A custom excludeGlobs list replaces these defaults. Keep the default entries when adding your own. The project’s exclude field adds project-specific exclusions. Files omitted from indexing cannot supply normal cross-file results.
Commands
Section titled “Commands”Open the Command Palette with Ctrl+Shift+P. English command names are listed below. PRO activation and project workflows are for invited closed beta testers; the presence of a command is not an offer of public PRO access.
| Command | Purpose |
|---|---|
| SolidCAM GPPL: Open Server Logs | Open the current daily server log. |
| SolidCAM GPPL: Synchronize Procedure Documentation | Since 1.7.0: update XML parameter tags from the current procedure signature, preserving descriptions. See documentation synchronization. |
| SolidCAM GPPL: Activate PRO License | Activate a supplied beta license. |
| SolidCAM GPPL: Refresh PRO License | Ask the licensing service to refresh the local license. |
| SolidCAM GPPL: Create gppl.project.json | Create or open the project manifest; requires active PRO. |
| SolidCAM GPPL: Refresh Project Explorer | Refresh the GPPL Project tree; requires active PRO. |
Beta request configuration
Section titled “Beta request configuration”Public license and trial requests are not open. The settings below are retained as a reference for beta builds; they do not provide public access to PRO.
solidcam-gppl.proRequestUrl, solidcam-gppl.proRequestEmail, and solidcam-gppl.proRequestToken configure the request destination. These are application settings, normally supplied with the extension. The URL takes precedence over the email fallback. Invited testers should change them only under instructions from their beta testing contact; activation uses the serial-number workflow described in Licensing.