(Build b737) – 23 Aug 2014
- Clarify exception lists for several comma delimited lists.
- Corrected a bug in MISRA 2008 rule 6-4-1, MISRA 2004 rule 14.9 and All Check script ifConstructShallBeFollowedByACompoundSatament.upl where preprocessor directives inside of defined functions was not handled correctly.
- Added MISRA 2008 rule 9-3-3 and All Check script methodsMadeConstOrStaticIfPossible.upl to Code Check.
- Added MISRA 2008 rule 10-1-3 and All Check script accessibleBaseClassNotBothVirtualAndNonVirtual.upl to Code Check.
- Fixed date format default values for editor printouts.
- Fixed an issue where if there were a released window and a non-released window editing the same file, on project close and then open, the file would not come back as a released window.
- Fixed regresssion in build 736 that caused some editor file context sub-menu items to fail.
- Prevent error on cytoscape import caused by <> in the longname of entities.
- For assembly, Python, Java, Jovial, Pascal, Ada, C#, Fortran, and web languages, made changes to give error message for files too large to open.
- Fixed regression in build 733 that caused ‘base’ references to sometimes be confused with ‘use’ references.
- Fixed missing define references for variables defined in lambda expressions.
- Fixed static member function kind.
- Added missing references to C++11 type aliases and type alias templates.
- Allow user tools hierarchy to have any level of nesting.
- Fixed crash in uperl lexer when a c++ file ends unexpectedly in an inactive preprocessor region.
- Add support for MSVC 2013 C# projects.
User Andrzej has shared his User Tools for performing Version Control operations in Understand. Similar to our posts on using SVN and CVS commands in Understand.
To install just go to Tools->User Tools->Import
We finished our official testing this morning and are happy to announce support for Windows 8.1. Our testing was done with Understand 3.1 build 694 – however earlier builds of Understand will probably work just fine.
Diving into the API documentation can be a little overwhelming, so here is a collection of tutorials to get you started.
With build 642 we’ve added an awesome new feature called Background Parse. It is designed to let you get right to work on your project as soon as Understand opens, instead of needing to wait for the parse. Right away you’ll have access to the Project Browser and Editor windows, and as soon as the parse is finished, everything else will be available.
Other features added since the release of Understand 3.0:
Added build system monitoring with buildspy
Added support for Windows 8
Improved project building capability
Improved Visio Export
Added ability to annotate code
For those that like to live on the bleeding edge, we have tested Understand 3.0 with Windows 8 and they are fully compatible. You can grab the latest build of Understand here.
We are happy to announce support for directly exporting graphs to a Visio compatible file.
In the past we have used the Visio API to export Understand’s graphs to Microsoft Visio. Understand would attempt to launch Visio and use the API to interactively draw the graph in Visio. There were several problems with this approach, the nodes and arrows of the graphs were not adequately connected, and in some cases the API would refuse to launch Visio. Of course this approach also required that Visio itself be installed on the same system as Understand.
Some graphs also have an option to export to the graphviz .dot format. This option is only available to newer graphs that are generated using the graphviz engine in Understand. Some older graphs use a different layout engine so that option is not available for them.
We are excited to announce the release of Understand 3.0 (build 611 and later).
We don’t like to make you wait for new features, so many of these features were already added in beta form and you may be familiar with some of them. There is an updated manual covering all of these new features, and several new floating licensing options are also available. The upgrade to 3.0 is free as long as your maintenance is up to date and Understand 2.5 and 2.6 Licenses will also work with Understand 3.0. Grab Understand 3.0 here
Features Added Since Understand 2.6 Release
New Floating Licensing Options
Node-Locked Floating License
A node-locked floating license is designed for a single machine that many users will be accessing, such as in a lab or a secure environment. It is similar in concept to a Standard Floating License but no license server is needed, and it will only work on the one machine.
USB-Dongle Floating License
This license is ideal when the license needs to be shared between different people on different networks, or if there is a lot of traveling involved. The license is mailed to you on a USB drive. As long as that drive is attached to the computer, Understand will work. The license dongle can be shared between users as needed.
Dongle licenses expire after two years and will need to be replaced. There is an additional fee for new and replacement dongle licenses to offset the setup and shipping costs.
We just added a plugin to identify duplicated lines of code. You can grab it in the API/Plugins section of the support page.
Update April,26 2012 – I’ve made some extensive changes to this script to improve performance and remove repeated results
Structure101 has several great tools for analyzing and refactoring your code base, and they have just finished adding the ability to import Understand projects into their tools. You should definitely check it out.
As an extra incentive, they are offering a free license to the first 3 Understand users who demo one of their tools and send an exported image such as the one below of any part of their code or an Open Source project. Just send it to email@example.com and tell them Kevin sent you
To be fair to another great partner, Lattix can also import your Understand projects and is a great tool for organizing and refactoring your code, so give them a look.