MICROGDS 7.1.2 RELEASE NOTES July 2003 ============================ MicroGDS 7.1.2 is provided as a patch to your MicroGDS 7.1 installation. The patch will upgrade both MicroGDS7.1 and MicroGDS7.1.1 installations. It will not work on a machine that does not already have 7.1 installed; nor will it work on a machine which has already had MicroGDS 7.1.2, or any later patch, installed. It is for use ONLY WITH THE ENGLISH VERSION of MicroGDS; contact your distributor if you need a patch for another language version. If your MicroGDS 7.1 installation has been altered, or if you have applied any "hot fixes" since MicroGDS 7.1, the patch installation procedures may require access to the original installation state in order to check correctly for changes. Unfortunately the message issued by InstallShield is not always clear! Assuming you installed MicroGDS 7.1 from a CD, this simply means that you will need to reinsert your MicroGDS 7.1 CD into the CD drive before the patch installer can continue. IMPROVEMENTS AND FIXES SINCE MICROGDS 7.1.1 ------------------------------------------- We have made some changes to improve compatibility with future releases of MicroGDS. MicroGDS now tries harder to use relative filenames when saving data. Specifically, it inserts ".."s into relative names if required, provided that this doesn't involve going through the root directory ("d:\" or "\\atlas\temp") When attribute data clauses are used in a filter, MicroGDS could behave incorrectly in various ways. This is now fixed. Printing more reliably determines if the printer is colour or monochrome. Print preview displays in the correct colour mode for the chosen printer. MicroGDS now handles importing zero length Autocad text primitives, and Autocad polyface meshes with missing vertex records. It also correctly handles polylines up to 4095 vertices. Drawing could occasionally produce stange results especially on a multiprocessor PC. Editing an instance could sometimes could MicroGDS to crash. A problem with using OLE objects in conjunction with auto-backup has been fixed. We have provided a workround for a bug in Windows XP which causes external characters to be mis-positioned (this affects Far-Eastern character sets only). CadLineTo with a setedit restriction now forms connected lines in the same way as earlier releases. A Cadlink program listening for command callback events could fail to draw rubberbanded graphics correctly. This is now fixed. CFGetObjectMetaFile() no longer has a limit of 32767 for link numbers. IMPROVEMENTS AND FIXES BETWEEN MICROGDS 7.1 AND MICROGDS 7.1.1 -------------------------------------------------------------- The speed of drawing was slower under some circumstances, especially if the window contained many phases. This has now been fixed. Some users have also noticed that as of MicroGDS 7.1, more zoom operations show a rescaled raster image while the vector redrawing starts in the background. This behaviour is unchanged at MicroGDS 7.1.1. We are monitoring user reactions and will, if necessary, modify this behaviour in a later release or patch release. Disabling the display of the selection could cause a redraw not to finish. Applications could hang or error due to MicroGDS invoking event handlers inside a Cadlink call. Nested Photos could be incorrectly clipped. Set Name Dims Last Facet could generate multiple last facets. Double clicking on a shortcut to a MicroGDS document could cause a crash. Modifying the selection whilst the screen was being redrawn could sometimes cause the selection to be displayed incorrectly. A bug in BIF file opening has been fixed. Autocad export created Viewports on layer zero, rather than the layer which the original photo was on. Using Object Superimpose on an Instance could cause a crash. Using an output space filled linestyle sometimes facetted boundary arcs incorrectly. Creating a custom paper size from the MicroGDS Print Properties dialog would sometimes not leave the size selected. A bug causing Word to crash when the view was changed on an embedded MicroGDS document has been fixed. Changing the scale when creating a photo did not always work correctly. The text ^(Scale 0) caused an error.