If you are a new user downloading Manifold for the first time, please download your installation file from the Product Downloads page. That page has useful information for new users who are downloading Manifold for the first time, including links to other files you might want to download as well.

Installing and Using Updates

All updates require a working license of Manifold System 8.00. If you do not have such a license, you will not be able to use any of the updates.

Updates are provided for those users who can read the instructions and have the technical skills to download the update and install without technical support. If you have any questions regarding the download or installation of an update, that requires a technical support incident. See the Support page for information on tech support.

An update is identified by its version, which is a combination of four numeric values, such as 8.0.0.2279. You can find the version of your working installation of Manifold in the Help - About dialog. Versions of Manifold starting with 8.0.5.0 have the last numeric value equal to zero, which can be omitted.

All updates are cumulative. A newer update will include all fixes and enhancements issued in previous updates.

Installing an update will preserve the activation status of your working installation of Manifold and will not require spending new Activation keys.

Uninstall any prior Manifold versions BEFORE installing an update.

Be sure to completely uninstall the previous version of Manifold, to allow the update to install cleanly. Use the Windows Control Panel's Add or Remove Programs applet to uninstall the prior Manifold version. Problems with Windows installer during uninstallation? See the Windows Installer page for tips.

Login as Administrator to install an update. Use the actual Administrator account and not some other account believed to have administrator rights. Users logging in with a different account are sometimes surprised to learn they don't have true Administrator rights in Windows 7 or Vista. See the Administrator Login page for info on how to login using the actual Administrator account.

Please read the installation instructions
carefully before installing an update. If you are working with an older Windows system that might not yet have the .NET Framework installed on it, don't forget to install .NET Framework 4.0 (.NET Framework 4.0 is required, a change from prior Manifold updates).

To install an update, download it, unzip it and double-click on the .msi installation file to install it. Updates are large files, typically 80 to 100 MB, so you will need a reliable Internet connection to download an update without errors.

If there are any errors when unzipping the downloaded file, the file was damaged during download or was not completely downloaded. Try again or use a mirror server that may be closer. Users in distant locations with inconsistent Internet links might not succeed even with many tries. If you have a problem with a download, arrange for a colleague or consultant who has a reliable Internet connection to download the files for you.

Important Note for Third Party Applications: As of update 8.0.29.0 all third party modules created with updates before 8.0.29.0 that bind to Manifold DLLs such as Manifold.Interop.dll or Manifold.Interop.Scripts.dll must be recompiled, including standalone applications, class libraries and custom controls using Manifold objects, statically compiled extensions for web sites using Manifold objects, add-in panes for Manifold, custom image server and geocoding server modules for Manifold, and similar third party modules. Built-in image server and geocoding server modules for Manifold are an exception to this and should continue to work seamlessly.

Although in many cases modules using Manifold DLLs built for versions of Manifold prior to 8.0.29 may continue to work after upgrading to 8.0.29 correct operation cannot be assumed unless these components have been specifically tested against .NET 4.

If you are running a web server with one or more web sites which use Manifold IMS, or are running any other applications that use Manifold through the object model, do a clean reboot prior to installing the update.

Once an update has been installed, it is a good idea not to delete the .msi file used to install that update until after that update has been replaced by some future release. This will retain the .msi file for any future uninstallation / installation needs.

Click the links below to download from Manifold's primary servers. Click a flag link to download from a mirror server that may provide faster or slower downloads depending upon user location and server loads. The following updates are available:

553. (Fix) Computing a triangulation of an area can no longer produce flat triangles at the area boundary.

552. (Fix) Computing a triangulation or a Voronoi diagram no longer sometimes produces incorrect results on regular grids of points.

551. (Fix) Docking and undocking panes no longer sometimes fails to redraw the contents of the frame and component windows.

550. (Fix) Attempting to delete records from a linked table via a DELETE query no longer fails with an error.

549. (Fix) Converting text characters into vector shapes when rendering a layout to AI, PDF or PS with the "Text as graphics" option turned on no longer sometimes skips curve points on character glyphs.

548. (Fix) Importing an ERS file no longer sometimes fails to set coordinate system units to US Survey feet.

533. (Fix) Exporting a drawing to MIF / MID replaces end of line characters in text values with spaces, to avoid breaking MID files (was: end of line sequences, the fix extends handling of end of line sequences to non-Windows and malformed ones).

532. Messages for errors occurring during activation are made more specific.

529. Performing a transform in a map window preserves the transform target, if this is possible. (For example, previously, applying a transform to [Selection in <layer>] was resetting the transform target to [All Objects]. With the change, if the target layer still has selected objects after the transform, the target will stay at [Selection in <layer>].)

528. (Fix) Importing a coordinate system from PRJ no longer ignores values of datum parameters written in the PRJ file in case the datum name does not match these values or is not recognized.

527. Exporting a coordinate system to PRJ writes values of datum parameters with full precision.

526. (Fix) Exporting a coordinate system based on Eckert IV or Eckert VI to GSR no longer exports incorrect values for the center longitude parameter.

521. (Fix) Computing weight centroids no longer sometimes produces wrong results for areas with more than one branch.

520. (Fix) Computing minimal containing circle or centroid of an object no longer sometimes produces wrong results if the object contains a pair of points that are not equal, but very close to each other.

519. PostgreSQL data sources include preliminary support for PostGIS 2.0.

518. (Fix) Exporting a drawing to MIF / MID replaces end of line character sequences in text values with spaces, to avoid breaking MID files.

516. (Fix) Performing spatial computations in a query no longer sometimes misoptimizes distance scans by ignoring the value of the location precision parameter (eg, objects that are very close to each other are not reported as touching since the optimizer is too aggressive).

515. (Fix) Computing variance or similar statistics in a query no longer sometimes produces incorrect values due to overflow.

8.0.26.0 - no longer available.

514. The installation logic is updated to allow running Manifold 8 together with future versions of Manifold on the same machine.

492. (Fix) Importing an XYZ file with only one row or column of pixels no longer supplies created components with a malformed coordinate system.

491. (Fix) Creating a layout with a template no longer leaves half-created layout in case the template could not be applied.

8.0.20.0 - no longer available.

490. The change coordinate system dialog shows the type of datum conversion to be applied near the bottom right corner of the coordinate system parameter list. Available datum conversion types are "NADCON", "NTv2" and Molodensky (default, shown as a blank string).

489. The coordinate system dialog shows the full name of the selected datum in a tooltip, if that name is too long to fit into the combo box.

488. (Fix) Importing or linking a CSV file no longer converts large numeric codes to 32-bit integer values and instead imports them as text, preserving all data.

487. Attempting to use a table with more than 2 GB records (eg, a virtual table for a large image) in a query throws a descriptive error message.

486. (Fix) Applying a layout template to a bound layout can no longer convert main layout elements to ordinary layout elements displaying the same component.

485. (Fix) Rendering an image linked from an image server no longer sometimes (very rarely) rejects a tile returned by the server in favor of data rendered from a less detailed zoom level, due to a race condition.

484. (Fix) Using the 64-bit version of Microsoft Access Database Engine 2010 no longer sometimes crashes.

483. Attempting to import or link an HTML file in 64-bit mode tries to use the 64-bit version of Microsoft Access Database Engine 2010.

482. (Fix) More Like This Cell and other commands working with rank columns treat lookup columns as text.

481. (Fix) Assigning to the Scale and ScaleAbsolute properties of the MapControl object no longer incorrectly multiplies respective scale by submitted value.

8.0.19.0 - no longer available.

480. Attempting to connect to a Jet data source in 64-bit mode no longer throws a "no 64-bit Jet" error message on failure.

479. Attempting to import or link an MDB or XLS file in 64-bit mode tries to use the 64-bit version of Microsoft Access Database Engine 2010.

478. The installation packages no longer contain geocoding servers for Geocoder.US and Microsoft Virtual Earth, which have been moved to free downloads for easier maintenance.

467. (Fix) The Manifold WMS server no longer sometimes reports wrong bounding box coordinates for coordinate systems other than lat/lon or that of the served component.

466. (Fix) Rendering compressed images (imported or linked) at high zooms no longer produces wrong results in case the coordinate system used for rendering differs from the coordinate system of the image (a regression).

8.0.17.0 - no longer available.

465. The GPGPU readout in the Help - About dialog indicates the presence of Fermi devices.

338. (Fix) Importing or exporting a coordinate system from or to a PRJ file correctly handles Greek coordinate systems. (First reported by Alexandros Malounis.)

337. (Fix) Adding a coordinate to a segment of a drawing object in a map window no longer uses wrong coordinate values if the coordinate system of the drawing differs from that of the map. (First reported by Asko Kontinen.)

333. (Fix) The Value() function in the Surface - Transform dialog no longer fails to work.

332. (Fix) Performing a transform on a linked drawing no longer fails to stop with an error if it can not write data to the drawing during the metric normalization phase.

331. (Fix) The report of the number of coordinates in the surface interpolation dialog is no longer misleading. (Thanks to Colin Driscoll.)

330. Components linked from the same PostgreSQL data source share the same database connection.

329. (Fix) Using data on a PostgreSQL data source no longer sometimes leaks a database connection.

328. (Fix) Attempting to delete a running script (eg, while it is stopped on a breakpoint) no longer succeeds. (First reported by Klaus Engelberg.)

327. (Fix) Using CUDA on a large surface no longer sometimes runs out of resources due to module leaks. (First reported by Ben Sigrist and Kevin Ross.)

8.0.5.0 - no longer available.

326. (Fix) The ActiveX control no longer sometimes fails to display properties in a property sheet.

325. (Fix) Shutting down an external process hosting Manifold code (eg, a worker process spawned by a web server [W3WP for IIS 6] or an external application using Manifold via the object model) no longer sometimes crashes due to an incorrect shutdown sequence.

292. (Fix) Copying and pasting a drawing or table no longer sometimes mangles columns used by viewbots. (First reported by Tim Baigent.)

291. (Fix) Rendering a line or point with a composite style no longer sometimes fails to render all parts of a style. (First reported by Klaus Engelberg.)

290. (Fix) Refreshing data in a component linked from a query no longer sometimes crashes in presence of circular references created via relations.

289. (Fix) Attempting to edit an object in a theme window no longer fails to pop up the Edit toolbar.

8.0.1.2316 - no longer available.

288. (Fix) Deleting a component no longer sometimes causes Manifold to crash if the component is shown in several windows and the project includes a linked table. (First reported by William Howell.)

287. (Fix) It is no longer possible to use the Relink command on a table bound to a (linked) drawing. (Thanks to Klaus Engelberg.)

286. (Fix) Connecting to a PostgreSQL data source no longer sometimes fails to locate and use the geometry type. (First reported by Hartmut Tschauner.)

285. (Fix) The Edit - Go To command no longer fails to recognize views for a theme component.

284. (Fix) The Edit - Go To command no longer fails to recognize saved selections for a theme component.

283. (Fix) The scale combo in the Navigation toolbar and the Edit - Go To command no longer provide the "Selection" choice for a theme component. (First reported by Gloria Dangerfield.)

282. (Fix) Zooming a map window to a theme layer / selected objects in a theme layer no longer fails to recompute the area to zoom to after zooming correctly for the first time. (First reported by Gloria Dangerfield.)

281. (Fix) Exporting a coordinate system to a PRJ file correctly exports the scale of the used unit.

280. (Fix) Importing a coordinate system from a PRJ file recognizes user-defined units and adjusts the values of the local scale parameters according to the unit scale. (First reported by John Mechalas.)

279. Reading the Caption property of a UserInterfaceDialog object returns a blank string in case the dialog has already been closed. The change makes it easier to implement code waiting for a particular dialog to appear.

278. (Fix) Setting the file type in the standard Windows file dialog to "Data Sources ()" or a similar choice via a script no longer fails to close the dialog. (First reported by Ketch Lorne.)