Products, the Universe and Everything

The Riverblade Developer's Blog

Beth demonstrating Visual Lint at the ACCU Conference 2008  Anna taking part in a discussion panel at the European Software Conference 2007 

Welcome to our developer's blog. We hope that this forum provides an insight into us, our products and how we develop them. Please feel free to write to us if you have anything to add to any of the posts here.

Current Entries | Archives |

How to change the font used in the Message Lookup Display
Wednesday, May 21, 2008

By default, the Message Lookup Display uses a Courier font for displaying the details of selected messages. Although the font used in the display is not configurable via the user interface, it can (as can be seen in the screenshot below) be configured using the registry:

The Message Display can also use a user defined font (in this case Consolas 10 point)

To do this, all you have to do is set the following registry keys to the font name and size (in points) you wish to use:

HKEY_CURRENT_USER\Software\Riverblade\Visual Lint\Settings\Displays\Warning Lookup\Font Family
HKEY_CURRENT_USER\Software\Riverblade\Visual Lint\Settings\Displays\Warning Lookup\Font Size
For the settings shown in the screenshot (Consolas 10 point) we have created a registry export file that will do this for you without having to fiddle around in the registry editor. Feel free to download it and modify to your preferred font settings.

As an aside, the reason we haven't added any specific controls to the user interface to set this is that the intention has always been that the font used would be linked to that of other comparable windows in the IDE. Unfortunately that code hasn't been written yet, so the registry is (for now) the way to do it.

Posted by Anna at 10:06 | Get Link


Visual Lint has been released
Wednesday, May 07, 2008

The changes in this version include:
  • Added update checking, via an Installaware scheduled task (note that the product update check is scheduled from a checkbox on the completion page rather than the InstallAware default of on the next login). Start menu entries for manually defining the update schedule and manually checking for updates have also been added.

  • Improved the prompt shown by the Configuration Wizard when the PC-Lint installation folder cannot be located.

  • If a background analysis task causes a manual analysis task to abort, the manual analysis dialog will now be closed.

  • Corrected a validation bug in the Configuration Wizard [IMS ID 261].

  • Replaced std::sort with std::stable_sort to ensure deterministic secondary sort ordering in the Analysis Status and Results Displays.

  • If an ATL exception occurs during the solution/workspace loading process, a message box will no longer be shown - the warning will instead be logged to the status window.

  • Inherited property sheet (.vsprops) file specifications of the form ".\FolderName" are now parsed correctly (applicable to VS2002, VS2003, VS2005 and VS2008 IDEs).

  • Preprocessor directives defined within inherited property sheet (.vsprops) files are now included within the returned project configuration (applicable to VS2002, VS2003, VS2005 and VS2008 IDEs).

  • Corrected the ordering of additional include folder specifications inherited from a .vsprops file.

  • When a lint issue is double clicked on in the Analysis Results Display under Visual C++ 6.0 or eMbedded Visual C++, the selected line is now more appropriately positioned within the code editior.

  • ".\" additional include paths are no longer filtered out when project.lnt files are written.

  • If the "LINT" environment variable is set, Visual Lint will now issue a warning in the status window and clear it within the process (this change is necessary to prevent the injected command line parameters causing analysis failures. If required, the same effect can be achieved via the "Custom Analysis Options" control on the "Command Line" options page).

  • Corrected a bug in the Analysis Results Display which was preventing the "Go to Reference" command from working if the selected item was the first item in the display.

Posted by Anna at 00:03 | Get Link


LintProject has been released
Tuesday, May 06, 2008

The changes in this version include:

  • Removed all MFC dependencies. LintProject now uses ATL 7 directly, and in consequence, the source now requires Visual Studio .NET 2002 or later to compile (project files are supplied for Visual Studio .NET 2003 and Visual Studio 2008, but porting to other versions should be straightforward).

  • Converted the build to Unicode.

  • Added support for eMbedded Visual C++ 4.0 workspaces and projects.

  • Solution and project specific environment variables $(SolutionDir), $(ProjectDir), $(InputDir) and $(ConfigurationName) are now set during analysis. Our thanks to Andrej Pohlmann for contributing the code to implement this feature.

  • If a file of the form <project filename>.options.lnt is found in the project folder, it will now be used in the analysis command line. Our thanks to Andrej Pohlmann for contributing the code to implement this feature.

  • Added error checking for solution/project configurations. Attempting to analyse an invalid configuration will now cause an error to be generated.

  • Visual C++ 6.0 project (.dsp) files containing only one project configuration are now parsed correctly.

  • Added a "/exclude" parameter to allow specified projects to be excluded from analysis (our thanks to Andrej Pohlmann for contributing the code to implement this).

  • Integrated the solution and project file parsers from Visual Lint, along with various utility functions.

  • Corrected a potential buffer overflow in the loading of XSL stylesheets (thanks to Mark Ridgwell for identifying this).

  • Corrected a bug in the parsing of intermediate file folders within Visual C++ projects.

  • Reinstated a missing -u option in the analysis command line.

  • Added the application version to generated reports.

  • Fixed a potential COM exception in Utils::RefreshAllOpenBrowserWindows().

  • Fixed minor lint issues.

  • The code is now released under the Code Project Open Licence (CPOL) v1.0; file banners have been updated accordingly.

Posted by Anna at 23:43 | Get Link