Hi,

Thanks for the post.

1)
The shortcuts via tools hidden are supposed to be read-only but it makes sense to ensure changes are saved so will look at adding the "save all"

2)
Editing sources using toggle hidden files is not recommended. Using editable local libraries instead in "project\src\_micro-api\libraries" was the preferred way to have editable libraries in the project. This is because the libs are correctly referenced into the project and also known to be editable.

3)
Recent updates of visual micro provide a better way to edit libraries using shared c++ projects. This is now the recommended method and in your case "toggle hidden files" should not be used.

shared libraries between projects or make editable libraries

4)
It would be useful to see a verbose build output because toggle hidden files should have correctly resolved the tool chain paths. However there are a massive number of different board tool chains around at the moment so it's possible a new "known" tool chain version needs to be registered in visual micro. The verbose output will help to see what board and hardware version you are using so its always worth providing it. You can email the output as .txt to info[at]visualmicro.com along with a link to this post or post here.