CodeCheck can be set up to run from the command line using Und if that is your preferred work environment, or if you are looking to automate the task. To see all of the options available in Und, run und help. For specific documentation on each option run und help optionName.

To run CodeCheck from the command line, first you will need to export the CodeCheck configuration file from the Understand GUI that has the checks you wish to run selected.

Once that is saved to a file, the command line option is

und codecheck C:\path\to\configuration.ini C:\path\to\OutputDir  

Where configuration.ini is my saved configuration file and the results are saved to the OutputDir. 

Help us prove that not all programmers are anti-social, join our Facebook Fan page!

One of our users, Chris Johnson, has developed a .NET sdk wrapper for the Understand API.

I have written a .NET sdk wrapper around the understand API during the early spring and last fall. I wrote it because I didn’t want to use Perl anymore, and I wanted the strong type safety of .NET along with it’s wonderful debugging tools.
The API is written in managed C++ (i.e. C++/CLI), and once compiled, can be accessed by any programming language that targets the .NET framework.

More details at http://www.scitools.com/support/forum/viewtopic.php?p=5550

Thanks, Chris!

Several users have asked for a CVS user tool similar to the one Ken created for SVN

This is easy to do, and you can create your own User Tools to do many different things.

I went and bundled some CVS commands into a User Tool. Just import it via the Tools | Configure User Tools | Import button.

Download CVS User Tool

I haven’t used CVS in years, so let me know if I got anything wrong

Some of you may have noticed that the quality and timelyness of our support has improved this week. That is because I’m not there bugging everybody. My son and I are fishing on a lake in upstate New York.  Here I am with a 4 lb largemouth bass.  Normally I throw them back, but this one seemed just right to feed us this evening.  And it was tasty. The trip is almost over, so support will return to its slower lower quality form on Monday. 

In Part I I described how in Understand 2.0 we are attempting to have not SDI, or MDI, but “Any DI” – where you can put windows where you want and have them stay that way.  I described how you can move dock and information windows around in the GUI and anywhere on your monitor(s). In this segment I’ll cover document windows (editor and graph windows).

Here is Understand 2.0 with a couple tabbed editor documents and a tabbed graph:

(more…)