Type: Feature Request
#228 introduces a new concept for managing debug and run configurations.
This includes a separation of debug and flash download where the latter uses shell tasks to drive pyOCD. Yet, we run flash download tasks as debug prelaunch tasks to update the target device before debug.
It turns out there is a warning dialog if such prelaunch tasks take a little longer. Which can happen if you program large application images.
This warning looks scary from a user point of view.
You can suppress the warning with the following VS Code setting, for example per workspace in settings.json:
"debug.hideSlowPreLaunchWarning": true
We should write this setting to settings.json if not already set there. It could make sense to tie this to the launch.json/tasks.json update from #228.
Type: Feature Request
#228 introduces a new concept for managing debug and run configurations.
This includes a separation of debug and flash download where the latter uses shell tasks to drive pyOCD. Yet, we run flash download tasks as debug prelaunch tasks to update the target device before debug.
It turns out there is a warning dialog if such prelaunch tasks take a little longer. Which can happen if you program large application images.
This warning looks scary from a user point of view.
You can suppress the warning with the following VS Code setting, for example per workspace in settings.json:
"debug.hideSlowPreLaunchWarning": trueWe should write this setting to settings.json if not already set there. It could make sense to tie this to the launch.json/tasks.json update from #228.