RE: Visual Studio Code nRF Connect SDK improvements

user77782 — Mon, 13 Jun 2022 08:36:43 GMT

Hi,

From the team:

There's an outline available at the bottom of the explorer sidebar. You can also press the "bread crumbs" at the top (the file path > symbol name row right between the tab list and the editor
VS Code will always run a normal "build" unless the user explicitly requests otherwise - OR if the build system deems it necessary because of changes that affect CMake. See http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/develop/application/index.html#rebuilding-an-application
That is odd, we'll check whether we can reproduce this.
I think I would need some more info to understand what's going wrong here. There are several sources of errors - live editing error checking for the different languages as well as the build itself. When do errors appear and disappear? Is it related to editing, or building, or neither? Is it limited to specific languages, or does it happen in any file?
Unfortunately, we rely on Microsoft's solution for Go To Symbol in C files, which has been a bit spotty for us too. In Kconfig and DeviceTree, we're expecting this to work as it should, but we'd be interested in hearing about it if the problem occurs in those files too. In VS Code, you can only search in files that are part of the VS Code workspace. I'd recommend using "nRF Connect: Add nRF Connect SDK to workspace" to create a multi root workspace. Now, the search button in the source files in the sidebar works for the SDK as well.
We'll look into this. Any details on which repo fails would be appreciated.

We highly appreciate feedback like this. There are still parts of the user experience that was clearer with Segger Embedded Studio, but we rely on users telling us what works and what doesn't, as our own internal usability testing can't uncover all workflows and configurations.

-Amanda

RE: Visual Studio Code nRF Connect SDK improvements

user77782 — Wed, 08 Jun 2022 11:25:18 GMT

Hi,

Thanks for the feedback. I have forwarded it to the internal.

Regards,
Amanda