Sometimes it would be great to not have a CodeChecker run after a build has happened, eg. when fixing a bug, one would wish to just test if their code compiles properly but without the side-effect of losing bug path information.
The first approach could be a toggle button somewhere in the perspective – simply leaving the perspective does not prevent checking, and unloading the plugin is too much of a hassle.
An even better solution would be creating a separate Build without checking action (with an appropriate custom key-bind like Ctrl-Shift-b or Ctrl-Super-b(?)) with triggers a full usual build event but prevents CodeChecker from running.
(Of course, the next "non-preventive" build will have ALL the changes checked and presented.)
Sometimes it would be great to not have a CodeChecker run after a build has happened, eg. when fixing a bug, one would wish to just test if their code compiles properly but without the side-effect of losing bug path information.
The first approach could be a toggle button somewhere in the perspective – simply leaving the perspective does not prevent checking, and unloading the plugin is too much of a hassle.
An even better solution would be creating a separate
Build without checkingaction (with an appropriate custom key-bind likeCtrl-Shift-borCtrl-Super-b(?)) with triggers a full usual build event but prevents CodeChecker from running.(Of course, the next "non-preventive" build will have ALL the changes checked and presented.)