+CodeInspector - How To -
Quick scan of files, active forms, classes and projects
For scanning separate files, active forms, classes and projects it is recommended to use Quick Scan Window.
It is very convenient when you need to check one or a few files and there is no need to collect them into CI-project. Sometimes you need to check active project, class or form on the fly. In this case Quick Scan Window will be the best solution.
Firstly, before scanning of your source codes for errors you need to specify their type (field Type). Quick Scan Window supports three types of source codes:
- Files
This type of check allows scanning one or more files.
1) You can specify concrete file(s) by using browse [...] button or you can input path to the files and a mask using * and ? manually (E.g. c:\vfp\projects\abc\*.prg - for scanning all PRG-files in c:\vfp\projects\abc directory)
2) You can specify a folder to scan. All files under that folder will be checked for errors. - Active forms and classes
If there are any forms or classes opened in the designer, you can check them quick and easy by choosing this type of check. Just specify what form or class you want to check in the field Check. - Active projects
Checking active projects is similar to the previous type of check. All you need to do is to specify what project to scan (if there are several active ones) in the field Check.
Secondly, after you have selected type of check and specified source for scanning, you need to do one thing that will decrease number of errors in scan report. As the Quick Scan Window performs a check for standalone files, +CodeInspector do not know anything about some variables that are used in scanned files but are declared in external sources. As you should know - using variables that were not declared before - is an error. To solve this problem you need to specify list of all external variables or their masks on the Public mask tab of Quick Scan Window.
Use List public variable masks field to specify all external variable usage of which is not supposed to be an error. Use * and ? for variables masks and comma for separating variables in the list.
Thirdly, there is a checkbox Check internal procedures on the Inspector tab of Quick Scan Window. If you turn it on, all internal procedures in scanned source will be considered as standalone files and therefore using of variables that were declared somewhere outside the procedure but inside the scanned source will be treated as an error.
Now, everything is ready for scanning. Click on Start button and wait for all sources to be checked.
You can judge about results of scan by the counters in the middle part of Quick Scan Window:
First counter (Files) show the amount of total files and files that were checked up to the current moment. Second counter (Errors) show total number of found errors. There is a list of scanned files containing errors right under these counters. To view scan report on a specified file - double click on it in this list.
You can also export scan report to an external txt-file for further analyzing. Select scanned file with errors from the list and click Export button, specify file path and file name.
To finish work with Quick Scan Window – click Ñlose button.