Originally posted here: VSCode: Feedback/issues with developing an out-of-tree driver but moved to a new ticket as requested
The next major issue on my list would be the idle CPU usage and general lack of responsiveness of the extension
The above was captured after ~5 minutes of no code changes (project has been open for a long time) on an i7-12700. I'm also seeing noticable lag in the on-hover tooltips (lots of "Loading..." before displaying the content)
^^ Is taken from the C/C++ log view (log level turned to Debug). This is occurring with no files currently open and never seems to complete (correction, it does complete, just takes a *very* long time)
Speaking of inconveniences, Actions has a few edges that could be smoother
It would be good to be able to configure a few defaults for the actions buttons
- "Erase and Flash" is *much* faster than the default "Flash" action and I generally do not need to use the slower option. Would be great to be able to swap the default here
- Also would like to use this for "Debug" as well
- "Flash" action does a build first, "Debug" doesn't. While I do get the reasoning to allow this, making it the default is frustrating. An easy way to change this default would be greatly appreciated
- There is the "preLaunch" launch config option, but a) not sure how to refer to the build action and b) it hardcodes the build folder and again not sure how to get around that
