Errors are displayed in the Error Browser in a tree structure. The levels of the tree hierarchy are specified with the Group errors by drop-down lists to the left of the tree.
In this example, errors are organized by "Severity", and then by "Error Name":
You can expand branches of the error tree by clicking the "+" icon. Here we see the same tree with one of the branches expanded to show the individual errors:
Most errors are associated with a particular location in the project file, for example a particular block, tag, or file. Blue text in the error browser represents a hyperlink into the main browser. Clicking on this link in the error tree causes the associated location to be displayed in the main browser, and also causes error details to be displayed in the error details pane below the tree. The full text of the error message in the error details pane contains the same hyperlink, and may contain others.
Usually, the location of the error in the main browser is indicated with an error marker: . Clicking on the error marker causes the Error Browser to display that error. Mousing over the error causes the error description to be shown in the datatip.
If the "parent" (in the tree) of the error items is either Error Name or Error Code then just the link is displayed as the individual tree error items (because all the items will be the same kind of error). This the "short form" display.
If the "parent" is anything else, the error name and code will be included for each error item. This is the "long form" display. In the following example, the errors are grouped by Loop-PCU. There are a variety of different error types in each PCU. In Loop 1 PCU 4, there are instances of Error 266, Error 265, and Error 259:
In many cases, errors may be associated with more than one location in the project. For example, an error may reference two different blocks. In these cases, there is more than one link in the text of the error message, but in the error tree only the "primary" link is shown.
When you open the error browser, Hyperview stores information about the errors in the tree in a local database. Information about which errors are starred, hidden and reviewed is maintained in this local database.
When you load an updated version of your project file into Hyperview and open the error browser, errors that have appeared in the build since the previous version of the project file you looked at are highlighted.
To see the complete error documentation for any error type, click it in the error tree to display the error details in the lower Error Browser pane. Then click on [Help] or Complete error documentation to bring up the application help for the error in question. The application error documentation often contains screenshots and examples not included in the short summary documentation shown directly in the Error Browser.
Error details in the lower pane of the Error Browser can be cut and pasted via the right-click menu or Ctrl-C in the usual manner.
Note: On Windows Server platforms, a situation has been observed where this text copying does not work by default. This problem can be solved by disabling Internet Explorer Enhanced Security Configuration (the Error Browser details pane is an embedded Internet Explorer HTML viewer component). More information can be found here.
DBDOC ©1996 - 2018 G. Michaels Consulting Ltd., all rights reserved. Website largely available under the terms of the AGPLv3. Unless noted otherwise the following are products, trademarks, service marks and/or registered trademarks of their owners and/or holders in the U.S. and/or other countries. MediaView, Microsoft, Visual Studio and Windows are owned and/or held by Microsoft Corporation. AutoCAD is a registered trademark of AutoDesk, Inc. MicroStation is a product of Bentley Systems, Inc. 800xA, ABB, INFI 90, and Symphony are owned and/or held by ABB Group. RoviSys Turbo Lite Server is owned and/or held by The RoviSys Company.