CoCo Systems Ltd.    (Support Web)

Helping you become more productive, more creative.

 

 

Known Problems

The following is a list of the known problems with our software products. We are constantly working to eliminate any problems reported: fixes are made available via our downloads page. If you have a new bug to report, please do so using our Bug Reporting forms.

The bugs described below refer to particular versions of our software. To find out which version you have, choose the About command from the product's Help menu.

Choose a product:

Known problems and fixes or workarounds for our legacy products are described here.


VisiMap Professional

Version: 4.2

The following issues were discovered, all of which were resolved in VisiMap Professional 4.2 SP-1:

  • A map centre title of more than 255 characters will cause an exception when attempting to export the map to Microsoft Excel. This is actually an issue in Excel, not VisiMap Professional. The workaround is to use map centre titles of 255 characters or less.
  • The suggested filename is missing from the filename box in Save forms, and the displayed filename extension does not change according to the selected save file type.
  • In the MS Word export filter, an exception may be reported when creating styles that already exist.
  • When pasting a new branch, notes constructed from previously processed text may be erroneously added.
  • A badly-displayed and looping message box can occur when changing branch style to a header style via the Properties form. The workaround is to change branch styles via the Format menu.

Version: 4.1 SP-1

The following issues were discovered, all of which were resolved in VisiMap Professional 4.2:

  • Registration URLs are incorrect, following the re-hosting of coco.co.uk and visimap.com web sites.
  • The installer is missing a graphics support file needed by the Adobe Photoshop PSD export filter.
  • Minor issues in the client installer.
  • Promote command can sometimes be used on top-level branches, leading to unexpected results.
  • VisiMap Pro executable is not correctly marked as Terminal Server aware.
  • Error messages log file writing is broken.
  • Writing hyperlinks to exported Word documents can fail when using patched versions of Microsoft Word 2007.
  • Exceptions can occur when using links in "My Network Places" in file explorers.
  • In the MS Word export filter, the icon for hyperlinks generated from map links is missing.
  • In the MS Word export filter, map links to local branches are not exported as bookmark cross-references.

Version: 4.1a

The following issues were discovered, all of which were resolved in VisiMap Professional 4.1 SP-1:

  • An exception can occur when attempting to import a file.
  • When exporting to Word, a rare exception can occur when exporting style colours.
  • When launching an Outlook item, the item will sometimes display in plain text (rather than HTML) and erroneously appear as a draft message waiting to be sent.
  • In HTML-exported pages, the image map hotspot dimensions for maps in text outline view are incorrect.
  • Spaces in filenames referred to by HTML-exported maps are not handled correctly.
  • The text in the final page of the Web Update wizard is inaccurate.
  • Minor issues exist in the notes live spell facility.
  • The Web Update feature creates an (empty) updates folder below the main VisiMap Pro installation folder.

Version: 4.1

The following issues were discovered, all of which were resolved in VisiMap Professional 4.1a:

  • When Word 2003 or earlier is installed, VisiMap Pro sometimes erroneously unloads the Word export filter after startup. This could cause an exception to occur when attempting to export to Word and an error message to occur when attempting to access the Word export options. This bug does not occur when Word 2007 is installed.
  • The captions and message box/task dialog messages displayed by import/export filters are switched.
  • When PowerPoint 2003 or earlier is installed, the pptx export format (introduced in PowerPoint 2007) is erroneously displayed in the QuickExport bar and the File|"Save As" form. Attempting to it them, however, results in a meaningful error message.
  • When Word 2003 or earlier is installed, the docx, pdf and xps export formats are erroneously displayed in the QuickExport bar or the File|"Save As" form. Attempting to use them, however, results in a meaningful error message.

Version: 4.0 SP-3

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in VisiMap Professional 4.1 and later.

  • A DEP (Data Execution Protection) error can occur on some systems during installation.
  • On multiple monitor systems forms can become positioned off-screen when removing monitors or otherwise changing the virtual desktop arrangement.
  • On multiple monitor systems, the splash screen can display on a different monitor to the VisiMap Pro main form.
  • The spelling and thesaurus dialogs are sometimes positioned incorrectly on multi-monitor systems.
  • The 'mailto' prefix in the protocol drop-down list on the Add Link and Link Properties forms is handled incorrectly.
  • The Cancel button is unresponsive while downloading in the Web Update wizard and the Download Dictionaries wizard.
  • An exception is encountered when importing MS Project files containing empty tasks.
  • When closing, superfluous prompts may appear asking you to save maps which in fact contain no unsaved modifications.
  • The 'Revert to style' command on the Format menu does not work when the Properties Inspector is not displayed.
  • If misspelled all upper-case words are found by the spelling checker when the "Allowed cases" spelling option is set to 'Any', the suggested corrections can be in the wrong case.
  • The PowerPoint export filter is incompatible with older versions of PowerPoint.
  • When maps are saved to packages or sent by e-mail, links in the maps may not work properly when extracted from the package or e-mail at a different location.
  • The PowerPoint export filter is incompatible with OfficeOne's "Set Default Slide Layout" add-in.
  • When performing a refresh of the PowerPoint export filter's templates list, templates that no longer exist are not removed from the list.
  • Task precedence chaining in exported MS Project files is not correct.
  • In HTML exported files, the 'page top' hyperlinks do not work in some browsers.
  • In HTML exported files, the coordinates or hotspots in image maps are not always fit fully within the image's extents.
  • The fonts of radio buttons and checkboxes could display differently to other controls in some forms under Windows XP.
  • The map centre title is sometimes lost when adding open maps to a package.

Version: 4.0 SP-2

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 3 (SP-3) and later. If you are running version 4.0 SP-2 of VisiMap Professional, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • A startup exception will occur when running in trial mode on hyperthreading (HT) processors.
  • The default printer may occasional be misidentified when it is a remote share (which can cause VisiMap Pro to indicate a printer configuration error message).
  • A 'division by zero' exception may rarely occur on startup if no accessible printer is found.
  • Printing of maps will not succeed when the Print command is used on Windows Explorer's pop-up menu for map files.
  • Exceptions may possibly, but rarely, be caused by ill-timed auto-saves.
  • A gradual resource leakage may occur (caused by freeze checking code).
  • Some export filters incorrectly handle two-line branch titles (this can causes an exception when exporting to MS Project).
  • An exception that might occur after customising the main toolbars, if the 'Find in Files' or 'Open Folder' forms have previously been open in the same session and are now closed.
  • The Find/Replace form will fail to find text when used in the same session as 'Find in Files'.
  • An excessive delay (and memory consumption) may occur when opening the 'Add Link' or 'Link Properties' forms if there is a very large URL history in Internet Explorer.
  • Desktop shortcuts may not be created correctly from the file lists in 'Find in Files' and 'Open Folder' form (creation fails if 'Hide file extensions for known files types' Explorer option is selected).
  • There is the possibility of an exception when clicking on the Properties Inspector to switch to VisiMap Pro from another app.
  • There is some inconsistency in the adjustment of colours when the text and/or branch colours match the shading and/or map background colours.
  • The "A3 Transverse" paper size is erroneously shown as just "A3" in the Page Setup form's paper sizes list.
  • An exception might occur when saving maps containing a large number of Outlook links (especially when the map is password-protected).
  • Instabilities in the Styles form can occur after loading and modifying a different style sheet.
  • Changes to list items that are typed in (rather than selected from the list) in Properties Inspector form and Styles form are sometimes lost.
  • Wrong glyphs may initially display on copy-pasted links.
  • When an Outlook item is opened by double-clicking on it in the Manage Links form and then modified, the host map is not properly marked as modified.
  • Outlook item link edits are omitted from the undo/redo queue when edited by clicking on a link.
  • Due to a bug in some versions of Outlook, file-locking errors may occur when opening Outlook links.
  • When prompting to save changes to read-only files on closing, the Save As form is not presented for choosing a filename.
  • An 'invalid branch handle' error may possibly occur when importing maps.
  • RTF import restricts the size of documents to import to less than 2Gb.
  • RTF import does not properly handle (i.e., remove) page and section breaks in import documents.
  • A rare 'invalid font size' error might occur when importing RTF files with "Use default branch fonts and colours" option selected (due to a bug in the underlying MS richedit control).

Version: 4.0 SP-1a

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 2 (SP-2) and later. If you are running version 4.0 SP-1a of VisiMap Professional, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • Auto-saves can on rare occasions corrupt notes editing.
  • VisiMap Pro can freeze when a computer prepares to enter hibernation.
  • A freeze can occur on using the notes editor's Undo All command on WinXP SP1 or SP2.
  • An exception can occur when clicking with the mouse cursor on the status bar.
  • Detection of Simple MAPI-capable default e-mail client is not always accurate.
  • Multi-line error messages returned by external programs are not always displayed fully in VisiMap Pro error boxes.
  • A freeze report can could occur if Outlook takes an inordinate amount of time to load (e.g., on configuring or sending mail).
  • An empty page body can occur when previewing/printing a single branch's notes.
  • The strikeout checkbox in the Font form for the notes editor is not correctly obeyed.
  • An exception might occur when closing the Order Branches form.
  • A rare exception may occur when updating the Undo menu item.
  • Your template choices for the HTML export filter might be restored incorrectly after closing and re-running VisiMap Pro.
  • A file permissions error may occur when finishing the export of a map to Word 2000.
  • The suggested filename when saving new map which has 2-line map centre title is not correct.

Version: 4.0 SP-1

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 1a (SP-1a) and later. If you are running version 4.0 SP-1 of VisiMap Professional, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • Access violation exceptions can occur for some Win98/WinMe users in 4.0 SP-1 when starting VisiMap Professional or opening a map.
  • Rare freeze report can occur when finishing up a map export.
  • "Format too complex" error might occur when exporting to MS Word 2002.
  • Exception will occur on exporting an empty map to HTML.
  • Promote Children command is erroneously enabled when the map centre is selected, causing an exception if used.
  • When cutting a tree to a new map, or pasting branches as a new map, the new map's centre has the wrong shape.
  • The 'Map centre shape' drop-down list in the Preferences form does not display the shape glyphs.
  • Minor errors in on-line help contents.

Version: 4.0

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 1 (SP-1a) and later. If you are running version 4.0 of VisiMap Professional, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • There are a few minor on-line help issues ('How to...' command on Help menu, and a couple of broken browse sequences).
  • "Divide-by-zero" exception might occur on opening maps last saved in auto-fit map mode.
  • Possible exception when setting printer paper size.
  • Extraneous grey areas sometimes occur when printing graphical maps in 24-bit colour with 3D shadow.
  • Wrong scaling of partial print segments can occur when printing a graphical map.
  • When printing maps with the 3D shadow, full colour is sometimes used when a grey-scale option is chosen.
  • Importing of files passed via command line when VisiMap Professional is already open will fail.
  • MPX import filter: strings with embedded quotes are not imported correctly.
  • TXT import filter: error might occur on importing files with blank lines.
  • Exception might rarely occur when right-clicking an OLE object in branch notes.
  • Exception might occur during export to Word if the "Use VisiMap Pro page layout" option is unchecked.
  • Timed auto-saves are sometimes performed at an inopportune moment by VisiMap Professional. This can cause conflicts with other operations.
  • Exception will occur on closedown when colour palette is in a floating window.
  • The content of maps created when there is a Normal.mmt template is not initialised correctly.
  • Mouse wheel does not work in tree controls.
  • There are a few minor issues with tool bars.
  • An erroneous 'out of memory' error report might occur when exporting to HTML or graphic formats when map is displayed in auto-fit mode.
  • MS Project import filter is not resilient to MS Project errors when importing notes with embedded objects.
  • If there is no default printer defined, the start-up warning message is displayed even if the user chooses to suppress it.
  • An exception is possible when exporting to HTML, with Word 2000 installed (issue is due to improper handling of some auxiliary files that are sometimes created during the export process).
  • When cutting a tree to a new map, or pasting branches as a new map, the new map's centre has the wrong shape.
  • The 'Map centre shape' drop-down list in the Preferences form does not display the shape glyphs.

VisiMap Viewer

Version: 4.2 SP-1

There are currently no known issues with VisiMap Viewer 4.2 SP-1.

Version: 4.2

There are currently no known issues with VisiMap Viewer 4.2.

Version: 4.1 SP-1

There are currently no known issues with VisiMap Viewer 4.1 SP-1.

Version: 4.1a

There are currently no known issues with VisiMap Viewer 4.1a.

Version: 4.1

There are currently no known issues with VisiMap Viewer 4.1.

Version: 4.0 SP-3

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in VisiMap Viewer 4.1 and later.

  • On multiple monitor systems forms can become positioned off-screen when removing monitors or otherwise changing the virtual desktop arrangement.
  • On multiple monitor systems, the splash screen can display on a different monitor to the VisiMap Viewer main form.
  • The context sensitivity of the "Open Link" menu command is incorrect.
  • The fonts of radio buttons and checkboxes could display differently to other controls in some forms under Windows XP.

Version: 4.0 SP-2

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 3 (SP-3) and later. If you are running version 4.0 SP-2 of VisiMap Viewer, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • A gradual resource leakage may occur (caused by freeze checking code).
  • There is some inconsistency in the adjustment of colours when the text and/or branch colours match the shading and/or map background colours.

Version: 4.0 SP-1a

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 2 (SP-2) and later. If you are running version 4.0 SP-1a of VisiMap Viewer, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • An exception can occur when clicking with the mouse cursor on the status bar.

Version: 4.0 SP-1

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 1a (SP-1a) and later. If you are running version 4.0 of VisiMap Viewer, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • Access violation exceptions can occur for some Win98/WinMe users in 4.0 SP-1 when starting VisiMap Viewer or opening a map.
  • Minor errors in on-line help contents.

Version: 4.0

The following issues were discovered by us or reported by users, as listed below. All of these have been resolved in Service Pack 1a (SP-1a) and later. If you are running version 4.0 of VisiMap Viewer, we recommend you update to 4.0 SP-3 (see the Downloads page for details).

  • "Divide-by-zero" exception might occur on opening maps last saved (in VisiMap Professional) in auto-fit map mode.
  • Possible exception when setting printer paper size.
  • Extraneous grey areas sometimes occur when printing graphical maps in 24-bit colour with 3D shadow.
  • Wrong scaling of partial print segments can occur when printing a graphical map.
  • When printing maps with the 3D shadow, full colour is sometimes used when a grey-scale option is chosen.
  • Exception might rarely occur when right-clicking an OLE object in branch notes.
  • Mouse wheel does not work in tree controls.
  • There are a few minor issues with tool bars.
  • If there is no default printer defined, the start-up warning message is displayed even if the user chooses to suppress it.


webmaster@coco.co.uk
Last Modified: 24 May, 2018
Copyright 1996-2018 CoCo Systems Ltd.
All rights reserved.