VSCode does not mark current application target blue. Slow switching between build configurations. Etc.

RE: VSCode does not mark current application target blue. Slow switching between build configurations. Etc.

tesc — Mon, 22 Sep 2025 18:11:41 GMT

Hi,

Thanks for the update! I agree overall experience may suffer from unpolished corners, hence the appreciation for your feedback. I will let you know if we need more information, but for now it looks like we should have enough for recognizing and reproducing the issues. If anything, please continue using our tools, and report new issues if and when you experience them.

Regards,
Terje

RE: VSCode does not mark current application target blue. Slow switching between build configurations. Etc.

jakkra — Mon, 22 Sep 2025 11:50:17 GMT

Hi, the issues are small and not critical, for me I don't care too much, but the overall expereince is worse and might be a turn off for people evaluating the Nordic environment. So keeping the plugin as polished as the rest of the Nordic Environment I think i important.

Anyway, yes the issues above comes from that repo, but I see similar issues at work also (although application structure is similar there).

You can find the applications pre-defined here https://github.com/ZSWatch/ZSWatch/blob/main/.vscode/settings.json#L2 so you should open the root fodler in VSCode.

Let me know if there is anything more I can do.

RE: VSCode does not mark current application target blue. Slow switching between build configurations. Etc.

tesc — Mon, 22 Sep 2025 11:20:45 GMT

Hi again,

With the project, we would have much better opportunities for investigating further. Is it by any chance https://github.com/ZSWatch/ZSWatch ?

Regards,
Terje

RE: VSCode does not mark current application target blue. Slow switching between build configurations. Etc.

tesc — Fri, 19 Sep 2025 13:25:42 GMT

Hi,

Thank you for the reports. It is highly appreciated! We will look into the issues and see what can be done to fix them. Some are known issues, but it is always good to get more reports and more information.

I have experienced the debug popup previously myself, and it seems to happen when debug settings are configured using kconfig options only. The debug session itself seems to work as intended, though, so the main issue would be the popup popping up in situations where it should not do so.

Regards,
Terje