Extension Issue - new sketch using extension doesn't work #12

Most appropriate sub-area of Processing 4?

I'm not sure

Processing version

4.4.76

Operating system

Windows 10 19045

Bug description

After installing the extension, processing sketches in an already existing folder did not run, They start a processing process ( as shown in task manager ) but they do not show the sketch and stopping them using the button on the upper right does not quit the process, so clicking it many times spawns multiple instances that you have to manually quit in task manager.

I tried to create a new sketch using the processing button on the left panel that shows the sketchbook and examples, but that did not work, now after restarting vscode on an empty project and trying to make a new sketch; I get the following error

Error running command processing.sketch.new: Cannot read properties of undefined (reading 'uri'). This is likely caused by the extension that contributes processing.sketch.new.

Uninstalling and reinstalling the extension did not work.

Also both the sketchbook and Example panels both show

There is no data provider registered that can provide view data

So it looks like the extension is not correctly setting itself up.

UPDATE, it turns out if you do not have a folder already open in vscode, the extension doesn't work at all, you can't create sketches or folders for those sketches using the extension, This should probably be fixed so that when a user makes a new sketch and is asked where the sketch will exist, the extension creates the folder, opens it and then makes the sketch, this would avoid odd situations where you have to do odd setups in order before getting started.

So while I can now make a sketch, I still cannot run it.

Steps to reproduce this

"1. Install the extension

2. try to make a sketch using the sketchbook panel in the processing extension

3. error"

snippet

// Paste your code below :)

void setup() {

}

void draw() {

}

Additional context

No response

Would you like to work on the issue?

No, I’m just reporting the issue