Editing the `csolution.yml` file concurrently as file and via "Manage Solution" graphical view leads to confusion

[jkrech]

Description

There is a custom editor for the csolution.yml file that displays target-types, target-sets, project-contexts, build-type and debug adapter aspects graphically. The csolution.yml file can be opened as a regular YAML file in the editor. Both views cannot share a single buffer for technical reasons.

The proposal is to switch between both view and do not allow both views concurrently. When switching between the views the user will be asked to save or discard pending changes before the switch takes place. This updated content is re-read by the view being switched to.

If the Manage Solution View is open and an attempt by the user to open the file from the file explorer, there is a flickering as it gets briefly opened but then automatically closed before the user can see and edit the content.
This is a technical limitation we would need to accept:

Is this request a Security Requirement?

• Yes

[HansSchneebauer]

I think the current implementation in version 1.67.2-45-375a3a2 is not less confusing. I understand the limitation when the csolution.yml file is opened from the file explorer (this would be acceptable in my opinion), but this also applies to the buttons in the CMSIS view.

When the csolution.yml file is open and you press the 'Manage Solution Settings' button, the editor switches as expected (with a notification if the file was modified). However, when you do it the other way around, nothing happens, or just a flicker. Or with other words, as long as the 'Manage Solution Settings' are open, there is no way to open the csolution.yml file because the view will never change. I think this is not acceptable.

[jkrech]

This is under investigation right now, however opening the csolution from the "Explorer View" of VSCode should already be possible!