devtool modify workspaces are not consistent

[afreof]

If devtool modify is called from the command line, VSCode does not list the recipe in the “DEVTOOL WORKSPACE” section. The situation is even worse if the workspace is set up via the user interface but deleted via devtool reset: There is no way to remove the recipe from the “DEVTOOL WORKSPACE” section.

Probably the solution should be that VSCode takes the status from the workspace folder by checking if some folders and files exist instead of saving the status in its internal configuration files.

[deribaucourt]

Hello Adrian!

The extension doesn't automatically detect external devtool workspaces changes. You need to run the "Bitbake: Rescan Project" command which will update the workspace view as well as the associated .bbappend from your workspace in the recipes view. The reason it's not automatic is because it takes running the devtool status command which takes quite some time.

But there is still room for improvement. We could make it automatic by getting the location of the devtool workspace and adding a Node file watcher there. When a workspace [dis]appears, we could then either directly edit the view, or trigger a devtool status scan.

Although the current full-UI experience is not affected by this limitation. We always trigger appropriate rescans when a devtool command is fired.

[deribaucourt]

So we do not display the devtool workspaces out of an "internal configuration file". We parse the devtool status output.

[deribaucourt]

You can trigger the "Rescan" command through the command pallette (Ctrl+Shift+P), or by clicking the button shaped in a circling arrow on the Yocto Panel, or click the Yocto status bar.

[afreof]

Hi Enguerrand

Thank you for your response. That is at least much better than what I was assuming. And I also see that challenge for making it even better without taking some assumptions which might be wrong.

I'm going to close this issue.