What's new in SourceMonitor 3.5.8.15
Mar 26, 2019
- All bugs through number 261 have been fixed in this new version. Thanks to all SourceMonitor users who reported bugs and made suggestions for enhancements. Both are much appreciated.
New in SourceMonitor 3.5.3.328 (Apr 27, 2017)
- Features added:
- New export option to specify decimal point character.
New in SourceMonitor 3.5.0.306 (Jul 17, 2015)
- All bugs through number 225 have been fixed in this new version
- Export to CSV now has an option to set the value separator charactor
- Numbers are now displayed and exported with the correct decimal and thousands separator characters for the current Window language setting
New in SourceMonitor 3.4.0.283 (May 16, 2013)
- Enhancements and fixes:
- Enhanced log to console from script commands.
- Java: enhanced parsing to handle expressions such as: getP().add(new Grid());
- Java: not parsing methods in anonymous classes properly.
- C++: wasn't parsing some methods implemented in header files.
- Java: counting one erroneous statement at block level just inside a method.
- Java: Not parsing "}else{" construct correctly.
- C: Double counting some function statements, caused excess counts in Statements per Function metric.
- Not counting blank lines properly.
- Reorder checkpoints and change a checkpoint name: the wrong name is saved. Added check to prevent entering the name of an existing checkpoint.
- Can't open a read-only project. Now you can open the project but get an error if you try to save the project.
- Java: the less than symbol '
New in SourceMonitor 3.3.2.263 (Jul 25, 2012)
- Added a new project-level option to ignore blank lines in the Lines metric.
- Added the option to save all options in a Windows "ini" file instead of in the Windows Registry. This option is used when you have defined a Windows environment variable (SOURCE_MONITOR_INI_FILE) that contains the path to your "ini" file.
- Added a Find method to Method View, Checkpoint View and Source Code View so you can search for a method name, a checkpoint name, or a file name.
New in SourceMonitor 3.2.0.208 (Nov 8, 2011)
- Added log messages for additional processing states and errors (including rejection of UTF-8 files when the UTF-8 option isn't set)
- Added a new flag to the script language, that causes all log messages to me displayed on the console in addition to writing to the log file. (Note: the element has errors only displayed on the console.)
- Added display of file counts to the new checkpoint dialog
- Added a new element to the script lanuage to change the way the project file path is resolved. The element contents, if relative, are resolved relative to the current working directory. The new element, , can be used instead when you want relative pathnames to be resolved relative to the script file directory
- Added new raw number option for export of metrics to CSV file
- Added option to display measured maximum depth (instead of "9+" when measured maximum is more than 9)
New in SourceMonitor 3.1.5.190 (Sep 17, 2011)
- Fast project load option (new project file format). Old projects are converted automatically (original project file is preserved) if you opt to use the new format. Note: If you use command files, you may want to change the project file extension in your script.
- Option to define checkpoint files from an XML file (such as the one your IDE uses to define the properties of a project). Instead of searching a directory hierarchy for files with specified extensions, SourceMonitor can extract the source code files for a checkpoint from one or more XML files. Now you can create a project from source files scattered across one or more disks.
- Source code directories can be specified relative to the project file. If you move the project file along with the source code, you no longer have to edit the project properties to correct the source code base directory.
- Checkpoints can have different base directories. This is for developers who save each version of source code in a different directory and want to have each version in a SourceMonitor checkpoint. In a script, you can specify the source code directory for an existing project. This directory is used in the script command to create a new checkpoint, but the project properties are not changed.
- To accommodate Windows 7 security , the log file is in a new location:
- Users\Public\PublicDocuments\Campwood Software\SourceMonitor
- In addition, the previous log is preserved when you start up SourceMonitor.
- When you view the log file by clicking on menu item View | View Log File,
- you will see the previous as well as the current log in Notepad.
New in SourceMonitor 2.6.8.123 (Dec 16, 2010)
- Fixed bugs through number 136
New in SourceMonitor 2.6.3.104 (Jul 9, 2010)
- Fixed bugs 126 through 129.
New in SourceMonitor 2.6.2.102 (Jun 25, 2010)
- Added modified complexity, export of Kiviat diagrams
New in SourceMonitor 2.5.1.0 (Jun 1, 2009)
New in SourceMonitor 2.1.8.8 (Apr 14, 2006)
- All bugs through number 47 have been fixed in this new version. Thanks to all SourceMonitor users who reported bugs and made suggestions for enhancements. Both are much appreciated