Closed bigwave closed 9 years ago
Hi.
I think it is better to hardcode extensions, supported by cppcheck (like it is done in cppcheck-gui). I already have some hack for qbs based projects. File type filter will be another one (more proper however).
So, if user have some c++ files with unsupported extension then he should rename them to more traditional or check them manually (through check current document
option).
Made it. Now you can check it and decide if it suits your needs.
Looks good to me
If you use "Import Existing Project" to create a project for existing C++ code when you scan the project it scans all files. e.g. including .jpg files which gives you lots of errors like: download.jpg,1,error,unhandledCharacters,The code contains unhandled characters (character code = 0xd8). Checking continues, but do not expect valid results.
This adds an optional file type filter to the options and filters the file list passed in to include just those types