On some systems, some lines on CAD/CLD diagrams fail to appear. They may appear after the user clicks the diagram, refreshes the screen, scrolls, or changes the zoom factor.
This problem generally does not occur locally on new versions of Windows, beginning with Windows 8 and Windows Server 2012, or on older versions of Windows when desktop compositing ("Aero") is enabled. As such, on older Windows versions enabling an Aero desktop theme may fix the problem. On Windows Server, enabling Aero may require you to install or enable the Desktop Experience addon.
The problem may still occur when viewing Hyperview via Remote Desktop, even in cases where the problem would not be occurring locally.
In both the local and remote cases, enabling GDI+ drawing should fix the problem.
Due to technical limitations in the search system used by DBDOC, in the Search All Titles search results, colons (":") and semi-colons (";") are displayed as hyphens ("-"). To search for a title with a colon or a semi-colon, you need to enter a hyphen in its place.
Hyperview's default printing options do not work well with some printer drivers. The most common problem this causes is live data being visible in the printout in places where it should be hidden by something in front of it.
When Hyperview is first started, it does some analysis of the project file to speed up searches. If you are viewing a large project on an older computer, you may notice some slowness while it does this. This will go away after a few minutes, when Hyperview finishes its analysis.
Due to default security settings on Internet Explorer, which affect the embedded version use to display Error Browser entries, copying text from Error Browser entries silently fails on Server releases of Windows (and possibly other versions if similar security settings are set). However, printing and exporting errors should be unaffected, and if need be this can potentially be resolved through changing the relevant security settings .
If hyperview.exe is manually run on XP Service Pack 2, you may receive the error that "the procedure entry point GetLogicalProcessorInformation could not be located". You should instead invoke hyperview_XP_SP2.exe, a variant which avoids this issue. This should not be required with DBDOC 11.2 or higher; place contact GMCL if you are nonetheless running into this problem.
DBDOC ©1996 - 2021 G. Michaels Consulting Ltd., all rights reserved. All other trademarks and registered trademarks are the property of their respective holders. Website source largely available under the terms of the AGPLv3.