error on windows

[asoltan]

Installed version 0.3.0.

When making modifications to a file (flags.h), gutter is not updated. In fact I see no changes at all. The file I'm modifying is not associated with git source control.

I see following (repeated) uncaught errors in Runtime status:

• Cannot read properties of null (reading '0')
• 'c:\src\AviClear\Console\Source\Src\flags.h' not found

The path to flags.h above is correct: 'c:\src\AviClear\Console\Source\Src\flags.h'.

Here are my settings (User): ID	Description	Default
showUnsavedChanges.clearOnSave	clear decorations on file save	false
showUnsavedChanges.debounceTime	ms to wait b4 checking for changes(increase the time if the editor became sluggish)	500
showUnsavedChanges.gitPath	global git path, git-installation.	"C:\Program Files\Git\bin\git.exe"
showUnsavedChanges.schemeTypes	allowed files schemes	[ "file", "untitled", "vscode-userdata" ]
showUnsavedChanges.schemeTypesIgnore	ignore this schemes & dont show warning message when requested	[ "vscode-terminal" ]
showUnsavedChanges.scmDisable	disable gutter comments when (.gitignore) is found in root of the workspace	false
showUnsavedChanges.showDiffOutput	show changes diff in output panel	false
showUnsavedChanges.showInGutter	show changes in gutter	true
showUnsavedChanges.showInOverView	show changes in overview	false
showUnsavedChanges.styles	decoration styles	{ "overview": { "opacity": 0.75, "add": "#2faf64", "change": "#FFCE57", "del": "#a31515" }, "gutter": { "size": "auto", "add": "#2faf64", "change": "#FFCE57", "del": "#a31515" } }
showUnsavedChanges.terminalShellPath	custom terminal shell path	null
showUnsavedChanges.wholeLine	highlight multi-line block	true

Any ideas what could be wrong?

[ctf0]

i never tested on windows b4, but can u give a sample of the file to test with ?

[asoltan]

The problem exists with all the files, at least on my system. I am running on windows11. Do you still need a sample file?

[ctf0]

was the extension working with u on older version ? can you also tell me the version of your vscode ?

[asoltan]

I am quite sure it used to work at some point (~a year ago), but am not sure if it's due to changes in extension or vscode itself. I currently use version 1.95.1 of vscode, generally trying to keep it to latest.

Just tried using version 0.2.0 of the extension. Still same issue.

[ctf0]

hi again, am sorry i cant reproduce the error on mac & i dont have access to windows atm.