274. (Fix) The Boundary query function no longer returns incorrect data.

273. (Fix) The IntersectionPoint query function no longer fails to work if there are no intersection points.

272. (Fix) Canceling a Decompose to Triangles or a similar transform no longer fails to remove added objects.

271. (Fix) Shutting down the Manifold ODBC driver no longer sometimes produces an access violation error.

270. (Fix) Exporting an image or surface to an Oracle database using GEORASTER technology no longer leaks a small amount of memory.

269. (Fix) Exporting a floating-point surface to an Oracle database using GEORASTER technology no longer fails to use correct byte order for floating-point values.

268. (Fix) Setting the TransferDiv property of the Column object to TransferDivProportional automatically selects the parameter column.

267. The object model includes means to export and import data to and from SQL Server data sources using a script.

266. Reading and writing spatial data stored on SQL Server 2008 spatial represents coordinate systems using EPSG codes.

265. There is a new type of data sources for SQL Server, used to support spatial functionality in SQL Server 2008 spatial ("Katmai"). Communication with SQL Server is done via OLE DB. SQL Server data sources are only available in Enterprise edition and higher editions.

264. (Fix) The code in the default web page templates no longer sometimes fails to correctly pass blank string parameter values for multi-parameter queries.

263. User interface scripting objects support reading and writing values of items in list view controls, such as the list view in the contouring dialog.

262. (Fix) Attempting to find or replace text using regular expressions without case no longer sometimes fails. (First reported by Marjorie Roswell.)

261. Attempting to locate a pane using its name within a script allows omitting the component name postfix (for example, attempting to locate a pane named "Control Points" will succeed even if there is an active component, which sets pane name to "Control Points - [Component Name]").

260. Invoking a user interface command within a script allows specifying command context to access commands available in the various context menus and in panes.

259. Failing to reach activation servers checks for general Internet connectivity to validate proxy settings.

258. Attempting to get a new activation key over the web uses multiple paths to activation servers, for robustness.

257. (Fix) Table windows cut off lengthy string values which display as blank string values on Windows Vista systems.

256. The location precision values displayed by Administrator Console and related dialogs use regular, not exponential, notation. (First suggested by William Howell.)

255. The Topology Overlay dialog includes an option to force the use of Copy / Copy transfer rules (previous behavior) instead of the transfer rules defined in columns. By default, the option is turned off.

254. (Fix) Building an area topology no longer sometimes fails to assign disputed regions to one of the contending areas. Performing a topology overlay no longer sometimes produces incorrect results, frequently appearing as "leaks".

253. Importing or linking a "Manifold" drawing with a server-side spatial index managed by the Manifold spatial extender recognizes and uses that index.

252. Exporting a drawing using a "Manifold" drawing type with the geometry type set to "Geometry" or "Geometry (WKB)" to an instance of SQL Server with the Manifold spatial extender installed creates a server-side index managed by the extender. Using a server-side index provides for slightly better performance on reads, significantly better performance on writes, and makes writes more robust.

251. Transferring column values between objects in a linked drawing using Sample or Copy N-to-1 aggregates prefers blank strings to NULLs.

250. Picking a control point within a component window sets focus to that window. (First suggested by Colin Driscoll.)

249. Altering the formatting of a terrain with vector overlays for points preserves rotation angles for point symbols. (First suggested by David Brubacher.)

248. There is a new "Use GPGPU technologies (NVIDIA CUDA)" option in Tools - Options, Miscellaneous, which toggles the use of CUDA. By default, the option is turned on.

247. Importing or linking a DBF file as a table allows selecting columns to import or link.

246. The File - Import / Link - Table commands allow importing data from DB, HTML, MDB, WK, and XLS (in addition to CSV and DBF) files directly, without going through the data source selection dialog.

245. The dialog used to view and edit column values of a drawing object supports copying the list of shown values into the Clipboard.

244. The dialogs used to view and edit coordinates of a drawing object or label support copying the list of shown values into the Clipboard.

243. The object model includes means to convert lines with non-zero widths to areas, when importing DWG or DXF files. The ImportDwg and ImportDxf objects have acquired a new read/write property, Boolean WidenLines, which sets or returns the conversion of lines with non-zero widths to areas.

242. Importing a DWG or DXF file includes an option to convert lines with non-zero widths to areas.

241. The coordinates in the "lat" and "lon" tables within a NetCDF file are assumed to refer to the centers of pixels, instead of to corners, for registration purposes. (Thanks to Michael Sumner.)

240. Importing a NetCDF file supports importing data objects with 4 or more dimensions. (Thanks to Michael Sumner.)

239. Refreshing the caption of the main window during lengthy operations has been optimized to perform significantly faster when there is a maximized component window.

238. The system menu invoked by right clicking the caption of a dialog or undocked pane or toolbar includes a new "List Controls" command, which displays a list of programmatic names of dialog or pane controls, or toolbar commands, for use with user interface scripting.

237. (Fix) Importing a DWG file no longer sometimes (rarely) reads line coordinates in incorrect order.

236. (Fix) Importing a DWG or DXF file no longer imports with incorrect metric MLine entities that do not belong to a single plane .

235. Importing a DWG or DXF file with Z data no longer creates a Z column in object drawings, in addition to creating point drawings with Z data. (First suggested by David Brubacher.)

234. The OGC WMS server supports rendering transparent images.

233. Reading data from an SDE geodatabase reads parametric curves, flattening them into lines with straight line segments. (Thanks to William Howell.)

232. The Options dialog includes a new page for options related to logging. The "/logquerytime", "/logrenderingtime", "/logscripttime", and "/logtransformtime" command line switches override the values seen on the page for the current session of Manifold.

231. There is a new "/logscripttime" command line option, used to log the execution time of a script into the History pane. (First suggested by Lionel Huart.)

230. The "/logtransformtime" command line option has been extended to log execution time for the Surface - Transform dialog, spatial overlays and topology overlays.

229. The Options dialog includes a new page for options related to scripts. The new page includes an option to control the timeout used when scripting user interface elements. By default, the timeout is set to 120 seconds. (Both the page and option have been added in previous builds, but the implementation of the code behind the option has only been finished in this build.)

228. Window computations in the Surface - Transform dialog use NVIDIA CUDA technology if present.

227. Tile computations in the Surface - Transform dialog use NVIDIA CUDA technology if present.

226. Removing objects from a drawing linked from a table in the same project has been improved to perform significantly faster. A typical performance increase is 10 times or more.

225. Docked panes can autohide themselves when the user is not working with them. To make a pane autohide itself, click the "minimize" button near the "close" button in the pane caption. Moving the cursor outside the pane will then make the pane collapse to a small tab. Moving the cursor to a tab will reveal the pane. Clicking on the tab or clicking on the pane caption will show the pane permanently.

224. Importing or linking a drawing from a table with coordinate columns with an option to build lines using a dedicated column propagates that column to the created line drawing. (First suggested by Robert Heitzman.)

223. User interface scripting objects support scripting of the progress bar and slider controls, via the Text property.

222. Exporting a table to an ODBC data source tries to preserve the signed / unsigned variations of integer types when matching them to the types supported by the data source.

221. Filter computations in the Surface - Transform dialog use NVIDIA CUDA technology if present.

220. Curvature computations in the Surface - Transform dialog use NVIDIA CUDA technology if present.

219. Displaying a list of drawings available on a native Oracle data source hides drawings that have been deleted (are in a recycle bin of sorts).

218. Failing to save a MAP file, e.g., due to another user having the same file opened, prompts for the alternate save location. (First requested by William Howell.)

217. Deleting a set of drawing objects in a map can be undone. (First requested by William Howell.)

216. Names of scientific formats for numeric values used in table columns have been adjusted to correctly reflect the number of decimal digits used for the exponent. There are two additional formats that trim leading zeros in the exponent. (First requested by William Howell.)

215. Running an action query reports the number of affected records in the History pane. (First requested by Lionel Huart.)

214. Exporting a drawing to a KML file preserves at least 8 decimal digits in coordinate values and trims trailing zeros. This typically results in a file that is both smaller but more precise than before. (First requested by Martin Roseveare.)

213. Downloading levels of an image linked from a remote image server proceeds from least detailed levels to most detailed levels.

212. Removing a set of objects from a linked drawing has been optimized to perform much faster. A typical performance improvement is 2x to 100x and more, depending on the number of deleted objects.

211. Attempting to link a native drawing from a PostgreSQL data source detects the presence of a version trigger.

210. User interface scripting objects support scripting non-Manifold dialogs, such as the open file dialog. Names of controls are synthesized on the fly.

209. The DataSource object includes means to ping a data source to determine whether or not it is currently "alive".

208. The DataSource object includes means to import or link drawings, images, surfaces and tables using all available import and link methods.

207. The DataSource object allows configuring export columns when exporting drawings and tables.

206. The object model includes means to enumerate recently used data sources listed in the Data Source dialog.

205. The object model includes means to export drawings, images, surfaces and tables to all types of data sources, via the new DataSource object.

204. (Fix) Updating the contents of the MFD_META table on a SQL Server data source via the ODBC driver no longer sometimes fails due to a limitation in the driver.

203. ImportMdb and similar objects have been unified to use connection strings, import a single table at a time, and specify import columns.

202. Importing or linking a table from a database uses the new unified import code invoked by selecting the "Databases ()" import type. The old database import types have been removed. The import dialog uses the Data Sources list, and allows selecting import columns for all types of data sources.

201. Importing or linking a surface from a database uses the new unified import code invoked by selecting the "Databases ()" import type. The old database import types have been removed. The import dialog uses the Data Sources list, and includes means to import channels of native images and Manifold images.

200. Relinking an image supports linking to a native image (eg, an Oracle GEORASTER image) or a Manifold image.

199. Importing or linking an image or surface from a table with pixel records tracks progress when determining the dimensions of the target component.

198. Importing or linking an image from a database uses the new unified import code invoked by selecting the "Databases ()" import type. The old database import types have been removed. The import dialog uses the Data Sources list, and includes means to import native images and Manifold images.

197. (Fix) Canceling the export of a table or a Manifold drawing to a database no longer sometimes fails to remove the created database objects.

196. Importing or linking a drawing from a database uses the new unified import code invoked by selecting the "Databases ()" import type. The old "ADO.NET", "ODBC", "OLE DB" and other import types have been removed. The import dialog uses the Data Sources list, similar to Database Console, and includes means to import native drawings and Manifold drawings.

195. (Fix) Retrieving binary values larger than 64 KB from a native Oracle data source no longer fails.

194. There are means to change the coordinate system of a native drawing on a PostgreSQL data source.

193. Attempting to import or link a native drawing with a native spatial index from a PostgreSQL data source retrieves the bounding box of the drawing from the index.

192. Paths to recently used MAP files displayed at the bottom of the File menu have been shortened so that most of the path is still visible in most circumstances.

191. Saving a MAP file preserves file permissions on Windows 2000 and later systems.

190. Double-clicking an image in Database Console inserts the name of the table containing image data into the command pane.

189. Gaussian Blur and Motion Blur image and surface effects have been made more responsible to the Cancel button.

188. The About dialog reports the number of available NVIDIA CUDA devices.

187. The About dialog reports the manufacturer name of the CPU and the number of CPU cores.

186. Aspect and slope computations in the Surface - Transform dialog use NVIDIA CUDA technology whenever possible. CUDA is a technology that allows using stream processors present in modern GPUs for general-purpose computations, not necessarily related to graphics. For many tasks, GPUs can outperform CPUs by a factor of 10x and more. Right now, CUDA is only available for high-end NVIDIA graphics cards on 32-bit operating systems. Using CUDA requires installing a specialized driver available from NVIDIA. A typical performance increase from using CUDA for aspect and slope computations is 2x to 10x and more depending on the number of aspect / slope operations in the evaluated formula.

185. Dialogs displaying connection strings conceal passwords in connection strings for PostgreSQL data sources.

184. Double-clicking a data source in the Data Sources dialog selects the data source and closes the dialog. Adding a new data source automatically scrolls to that data source in the list. Starting a dialog automatically scrolls to the recently used data source in the list.

183. The performance of parsing coordinate system definitions has been significantly increased.

182. Loading a coordinate system from a PostgreSQL data source parses the name of the coordinate system from its definition.

181. Loading a coordinate system from a PRJ recognizes TOWGS84, AXIS and several other keywords.

180. The data type selection logic used when exporting data to an ODBC data source has been adjusted to work better for MySQL and other data sources. (Thanks to John Mechalas.)

179. Importing a surface from a NetCDF file recognizes "lat" and "lon" tables and automatically registers imported components to the values in these tables, provided they are spaced uniformly.

178. Closing a large number of component windows, e.g., during closing of a MAP file, has been optimized to perform faster.

177. Retrieving available coordinate systems from a database and matching a coordinate system (of an exported component) to the available systems tracks progress.

176. Administrator Console supports changing coordinate systems of drawings on SDE and personal geodatabases.

175. Unnamed coordinate systems used on databases are assigned names synthesized from their IDs (SRIDs).

174. Exporting a drawing to a database using the "Manifold" drawing type allows selecting the type of a geometry column.

173. The default name suggested for a component exported to a database has been modified to contain no whitespace characters.

172. The data source selection dialog automatically recognizes data sources which do not support storing drawings, images or surfaces. Attempting to select a data source which does not support storing components of a certain type during the export of a component of that type displays a warning message below the list of data sources and disables the OK button.

171. Exporting a query or table to a database uses new unified export code invoked by selecting the "Databases ()" export type. The old "ADO .NET", "ODBC", "OLE DB" and other export types have been removed. The export dialog uses the stored list of data sources, similar to Database Console, and includes means to specify the name of the exported table.

170. Exporting an image or surface to a database uses new unified export code invoked by selecting the "Databases ()" export type. The old "Oracle", "ODBC" and "OLE DB" export types have been removed. The export dialogs use the stored list of data sources, similarly to Database Console.

169. Exporting a drawing to a database using the "Manifold" drawing type supports creating a spatial index (without requiring Administrator Console).

168. The data source selection dialog saves the most recently used data source and automatically selects it upon startup.

167. Exporting a drawing to a database supports exporting a "Manifold" drawing, which is a table with a geometry column and some metadata in a MFD_META table. "Manifold" drawings are supported on all types of databases.

166. Exporting a drawing to a database uses new unified export code invoked by selecting the "Databases ()" export type. The old "DB2", "ODBC", "OLE DB", "Oracle" and "PostgreSQL" export types have been removed. The export dialog uses the stored list of data sources, similar to Database Console. (Exporting drawings to SDE data sources is no longer supported.)

165. Database Console reports the type of the heights channel for a remote surface, and the type of a remote drawing that is not native to the database ("Manifold", "ESRI Personal" or "ESRI SDE").

164. Administrator Console and Database Console store a list of recently used data sources and select the data source using a modal dialog.

163. Failing to add a new record to a linked table via a table window displays the error message returned by the data source and allows correcting the record values.

162. Database Console allows importing or linking drawings contained in ESRI personal geodatabases. Editing a linked drawing updates the spatial index.

161. Database Console lists drawings contained in ESRI personal geodatabases.

160. There are means to export surfaces as tiled images to databases. Exporting a surface creates an image with the usual BGRA channels and a separate channel for heights. Importing the heights channel re-creates the surface. The heights channel cannot currently be linked.

159. User interface scripting objects support "pushing" buttons in the drop-down portions of color, size, and style wells, which contain buttons for invoking the thematic formatting dialog, and similar windows.

158. (Fix) Importing a DNG or JPG image that has to be flipped or rotated according to the information in the image header no longer fails to place the resulting component into the current folder.

157. The performance of filtering large amounts of data using a generic spatial index has been significantly improved.

156. Displaying the value of a viewbot uses the format of the underlying column, if appropriate. (First requested by Robert Heitzman.)

155. Retrieving large binary values via ODBC or the native Oracle interface is more efficient.

154. Bit_Length and Octet_Length query functions have been extended to support binary values.

153. User interface scripting objects support scripting combo boxes, text boxes and other non-button controls in the toolbars.

152. Importing a surface from a NetCDF file recognizes and applies the value of the "missing_value" variable. (Thanks to Michael Sumner.)

151. Scripting the user interface supports scripting format lists such as the list of colors in the Display Options dialog for surfaces.

150. Saving of images and surfaces with compression has been adjusted to use a variation of the compression method which is more suitable for the new storage format. This improves performance at a small cost in the resulting file size.

149. Exporting a drawing or map to a DXF file cleans component names by replacing characters that are not supported by AutoCAD with spaces.

148. Scripting the user interface supports scripting color chooser and similar windows.

147. The performance of transforming surfaces using the Surface - Transform tool has been significantly improved. A typical performance increase is 2x on small surfaces, 10x on medium surfaces, and 100x and more on very large surfaces.

146. The performance of interpolating surfaces using triangulation adjusted for contours has been improved.

145. The object model includes means to control areas of interest of linked drawings. (Linked drawings created with prior builds of Manifold are not supported.)

144. There is a new "Area of Interest" command which edits the area of interest for a linked drawing. (Linked drawings created with prior builds of Manifold are not supported.)

143. Importing a surface from a raw ASCII file or from ESRI GRD file has been optimized to perform faster.

142. Undoing the effect of a Best Fit All Xxx command in a table window restores the sizes of all columns instead of just the last one.

141. Table window showing records returned by a query allows resizing columns using Best Fit Xxx commands.

140. Rendering of images and surfaces has been optimized to perform faster. Typical performance increase is 5x to 50x and more depending on the zoom.

139. Operating a WindowSet object in the context of an external application no longer throws an error and instead fails silently.

138. Changing the parameters of a generic spatial index no longer requires drop table permissions. Attempting to create a spatial index with bounds that do not include all coordinates of all drawing objects fails.

137. The Review pane works for maps.

136. Exporting an image to a database as a tiled table supports "deflate" compression for tiles.

135. Canceling the creation of a grid or graticule removes all created objects instead of creating an undo action.

134. Opening an add-in pane sets the initial size of the pane to that of the add-in control. (First requested by David Brubacher.)

133. Saving of images and surfaces that have not been changed since the file was loaded has been improved to perform significantly faster. A typical performance increase is 2x to 5x, not counting the effect from faster loading.

132. Loading of images and surfaces has been improved to perform significantly faster. Typical performance increase is 5x on small files to 100x and more on large files.

131. The storage format of images and surfaces has been improved to perform faster. Loading a MAP file with images and surfaces that use the old format automatically upgrades them to the new format (which takes time). Changing the values of pixels in an image or surface invalidates only those parts of intermediate levels that are affected by the changes. Composing intermediate levels has been improved to perform faster.

130. Exporting an image to a database as a tiled table correctly rolls back all changes upon a failure.

129. Exchanging coordinate system data with a native Oracle data source recognizes coordinate systems defined through parameter tables (a new feature of Oracle 10.2). Reading a coordinate system from a native Oracle data source has been optimized to perform significantly faster.

128. The object model includes means to save formatting to an XML string.

127. Attempting to alter data on an Enterprise storage based on Oracle works around some case-sensitivity issues in database drivers.

126. Exchanging geometry data with PostgreSQL supports (well, tolerates) data with Z and M values. Reading geometry data with Z and M values throws these values away. Writing geometry data with Z and M values inserts zeros.

125. Table windows showing records returned by a query allow showing and hiding columns and using the selection filter.

124. Creating a generic spatial index allows customizing the index level. Higher values produce more granular indices, which require more space but are potentially more efficient. For best efficiency, choose the level of an index proportionally to the number of objects you expect to have in the drawing. The value suggested by the Suggest button is a reasonable default.

123. The Windows dialog reports windows that display records returned by queries with the "(Table)" postfix, so that they can be distinguished from windows that display SQL statements. (First requested by William Howell.)

122. Progressive rendering for layouts caches viewport data for the last rendered layout element, to improve the performance of rendering elements with complex scopes. (Thanks to Patrick Weber.)

121. Highlighting saved selections in a drawing, image, labels, layout or surface window creates parallel views in the rendering cache, instead of throwing away all cached views for the context component.

120. Attempting to geocode a misspelled address against a geocoding extension database has been improved to operate much faster (by a factor of 20 and more).

119. Showing and hiding image channels via the Layers pane creates parallel views in the rendering cache, instead of throwing away all cached views for the context component.

118. Performing a topology overlay copies over the values in active columns, rank columns, and columns brought via relations.

117. Attempting to create a generic spatial index on a table that does not contain a primary key fails.

116. The format of MAP files has been changed to allow faster opens. Right now, MAP files open at about the same speed as before, but the new format allows making numerous improvements in this area in the future. Opening a MAP file locks it so that it can not be written to (but can be read from).

115. There are dozens of new datums for European countries. (Thanks to Manfred Beer.)

114. Custom datums and custom coordinate system presets support the "unit" attribute for datum rotation factors.

113. The object model includes means to script toolbars and panes in the main window.

112. User interface scripting objects support scripting toolbar controls. Each toolbar button is interpreted as a separate user interface control. (Combo boxes and text boxes within toolbar controls are not yet supported.)

111. When importing or linking a drawing, filtering objects in the desired area of interest using a generic spatial index has been made faster.

110. Running a script from another script spawns a new thread, in case the callee is configured to run in a separate thread. This allows freely mixing scripts that are configured to run in the calling thread or a new thread.

109. Form scripts can be configured to run in a separate thread, which allows scripting the user interface.

108. All Manifold dialogs have been adjusted to support user interface scripting.

107. Attempting to use the methods of the UserInterface object in a script that runs in the context of the main thread (has not been forced to run in a separate thread) throws an error.

106. The object model supports scripting of common Windows controls such as buttons, check boxes, labels, text boxes, list boxes, combo boxes, tree views and list views.

105. The object model includes means to script the user interface. This invokes running interactive commands and controlling dialogs and controls.

104. The object model includes means to force a script to run in a separate thread.

103. The properties dialog for scripts includes an option to force the execution of a script in a separate thread. Running a script in a separate thread allows using advanced scripting techniques such as scripting the user interface, but might be slightly slower. By default, the option is turned off.

102. Importing a TIFF file recovers from several common cases of corrupted headers.

101. The object model includes means to unlink linked components using a script.

100. The object model includes means to access the data source, rowset and technology of linked components using a script.

99. The rendering cache compresses cached views. A typical compression ratio is 1:10.

98. Database Console allows importing individual channels of tables with image tiles as surfaces.

97. Database Console allows importing or linking tables with image tiles as images.

96. Database Console recognizes tables with image tiles and shows them as images.

95. There are means to export images to ODBC and OLE DB data sources. Exporting an image to such a data source creates a table with a record for each image tile. Image tiles are stored in uncompressed BGRA format.

94. Editing a linked drawing with a generic spatial index updates the index.

93. Importing a surface from a NetCDF file automatically makes pixels with infinite or invalid floating-point values invisible.

92. Switching rendering of a layout from GDI+ or GDI creates parallel views in the rendering cache, instead of throwing away all cached views for the context component.

91. Rendering a drawing or a labels component with one of the Structure options creates parallel views in the rendering cache, instead of throwing away all cached views for the context component.

90. Rendering a graticule, grid, legend, north arrow, scale bar, control points, layout rects, or handles for the primary selected object is done after checking the rendering cache, to avoid re-rendering component data after changes to these visual elements.

89. Rendering part of a view that is in the rendering cache uses cached data. Therefore, decreasing the dimensions of a window that has been completely rendered always hits the cache.

88. Rendering a drawing, image, labels, layout, map, profile, surface, or theme stores last rendered views in the application-wide rendering cache. The size of the cache is 16 MB for 32-bit systems and 64 MB for 64-bit systems. The typical size of a view is 1 MB.

87. The object model includes means to set rendering options for IMS. Rendering options are specific to the rendering format.

86. Importing or linking part of a drawing in the desired area of interest using a generic spatial index tracks its progress and can be canceled.

85. Importing or linking an external table turned into a drawing via Administrator Console detects the presence of a generic spatial index (created within the same console) and uses it to restrict drawing data to the desired area of interest.

84. (Fix) Importing or linking a drawing from a native Oracle data source no longer interprets a NULL coordinate system (SRID) as Orthographic.

83. Drawing and label windows have been optimized to avoid caching the IDs of objects or labels in Z order, to start faster and spend less time updating after changes to underlying data. A typical performance increase in an edit-heavy session is 50% (2x).

82. Visual selection tools in label windows have been optimized to make better use of data generated by the rendering process. The performance increase varies with the amount of data (the larger the drawing, the larger the performance increase) and the bounding box of the selection shape (the smaller the box, the larger the performance increase). A typical performance increase is 70% (3x). Add and Subtract selection modes are fastest.

81. Visual selection tools in drawing windows have been optimized to make better use of spatial indices. The performance increase varies with the amount of data (the larger the drawing, the larger the performance increase) and the bounding box of the selection shape (the smaller the box, the larger the performance increase). A typical performance increase is 50% (2x). Add and Subtract selection modes are fastest.

80. Launching Manifold from the command line supports a "/logquerytime" option to log the running time of queries into the History pane.

79. Loading a MAP file with an image linked from a Manifold image server that is not installed on the system reports the problem and the name of the missing image server in the History pane.

78. Importing or linking a view from a native Oracle data source as a drawing assumes that the view has a spatial index (there is no easy way to detect this with 100% accuracy), and allows the user to specify the area of interest.

77. Layouts support progressive rendering.

76. The query parameters dialog automatically highlights the first parameter.

75. Rendering of drawings with minicharts has been optimized to make more effective use of spatial indices. The performance increase varies with the amount of data (the larger the drawing, the larger the performance increase). A typical performance increase is 30%.

74. Double clicking a cell in the new Spatial Index column in Administrator Console edits the spatial index with a dialog. The bounding box extents of the area covered by the index are editable.

73. The click target for the "close" button in the info bar window has been extended to cover the entire height of the window.

72. The maximum amount of text in the History pane has been set to 1 MB on NT-based systems. Attempting to exceed this limit automatically removes the oldest lines at the top of the pane to make room for new lines.

71. Maps support progressive rendering.

70. Lengthy operations such as transforms automatically suspend progressive rendering and resume it upon completion, so that the system does not lose time rendering what might be obsolete data.

69. Images and surfaces support progressive rendering. Except for image libraries and images linked from external image servers, There might be a slight delay before any of the image or surface becomes visible, but the system stays responsive to commands during this delay as well.

68. Labels support progressive rendering. There might be a slight delay before any of the labels become visible, but the system stays responsive to commands during this delay as well.

67. The Tools - Options, Rendering page includes the "Render data progressively" option, which turns progressive rendering on and off. By default, progressive rendering is turned on.

66. Progressive rendering gives preference to the active component window. If a user performs an operation that forces re-rendering in more than one opened window, the system will first attempt to completely render (progressively) the active window, then one of the other windows, and so on until all windows are up to date.

65. Drawings and themes support progressive rendering. During progressive rendering, the system renders data in parts updating the screen several times per second. The system becomes responsive to commands after rendering the first part of the data. (To see this in action, open a large drawing, watch the system render a part of it, then zoom in. The system will automatically restart rendering within the new viewport.)

64. Exporting data sets the default filename to that of the exported component.

63. The object model includes "get" and / or "set" methods for each parameterized property to allow using such properties from languages that do not (completely) support them.

62. Exporting a map to a KML file uses layer opacity. Folders for drawings with more than 10 objects are closed.

61. Exporting a drawing or map to a KML file ignores missing or blank field values.

60. Rendering of drawings has been optimized to better exploit data locality during the initial object sweep. A typical performance increase is 50% (2x).

59. Rendering of drawings and labels has been optimized to avoid performing extra bounding box tests during on-the-fly reprojection. A typical performance increase is 10%.

58. The NewLine query function has been altered to accept an arbitrary number of arguments. If all of the arguments are points, the result is a line with a single branch. If all of the arguments are lines, the result is a line with multiple branches. Otherwise the result is a NULL.

57. Importing a DWG file imports "ray" and "xline" entities.

56. Importing a TIFF file imports 16-bit integer and 32-bit / 64-bit floating point CMYK data.

55. Importing a TIFF file imports 16-bit integer LAB data.

54. There are means to export drawings to PostgreSQL data sources. There is an option to create a spatial index (on by default), and an option to create a sequence and an update trigger (on by default), similar to Oracle.

53. There are means to import and link drawings from PostgreSQL data sources. Reading data translates PostgreSQL geometry to Geom values. Writing data translates Geom values back to PostgreSQL geometry.

52. Creating a script in IronPython automatically adds references to the IronPython assemblies. To work correctly in all cases, the IronPython assemblies should be installed in the global assembly cache.

51. Interpolating a surface using constrained triangulation has been improved to produce smoother results in boundary triangles and in other extreme cases of interaction between contours.

50. The object model includes means to load a coordinate system from an AUX file.

49. The coordinate system dialog can load a coordinate system from an AUX file (a format used by ERDAS).

48. Importing a surface from a TIFF file with floating-point values automatically makes pixels with invalid or infinite floating-point values invisible.

47. Importing a TIFF file recognizes TIFF files with complex (as in, re+im) values.

46. The PRJ parser has been adjusted to correctly parse projection definitions with the "Authority" tag.

45. The object model includes means to set the rendering format and quality of IMS ouput.

44. Queries include means to interpolate from a set of points or contours using triangulation or constrained triangulation.

43. The object model includes means to export to and import tables from PostgreSQL data sources.

42. The object model includes means to convert geometry values to and from the Geometry (SDE) type.

41. Checking a Surface - Transform formula for syntax errors has been made faster.

40. The Surface - Transform tool includes means to interpolate a surface from a set of points or contours using triangulation or constrained triangulation.

39. Computing a constrained triangulation has been made more responsive to the Cancel button.

38. Importing or linking a drawing from a table using a geometry column can use the new Geometry (SDE) type. Doing that translates integer coordinate values within Geometry (SDE) values using offsets of 0 and a scale of 1.

37. Adding a new table column or changing the type of an existing table column can use the new Geometry (SDE) type. Changing the type of an existing geometry column to Geometry (SDE) translates geometry to integer coordinate values within Geometry (SDE) values using offsets of 0 and a scale of 1.

36. Interpolating a surface from a set of points has been made significantly faster (2x or 3x or more, depending on the data).

35. Interpolating a surface from a contour drawing using adjusted triangulation supports providing surface corner values.

34. Launching Manifold from the command line supports a "/logtransformtime" option to log time for drawing, image, surface and table transforms into the History pane.

33. Attempting to link an image using an image server module which returns an invalid coordinate system will proceed using the default coordinate system instead of failing with an error message.

32. Rendering area selection overlays using GDI+ makes more efficient use of rendering resources, to increase performance. A typical performance increase is 50%.

31. Rendering areas, lines and points using GDI+ makes more efficient use of rendering resources, to increase performance. A typical performance increase is 30%.

30. Exporting a drawing to an ArcSDE data source tracks its progress and can be canceled.

29. Exporting a drawing to an ArcSDE data source rolls back all changes in case of an error during the export process.

28. Launching Manifold from the command line supports a "/logrenderingtime" option to log rendering time for component windows into the History pane.

27. Exporting a drawing to an ArcSDE data source sets the drawing creation date in ArcSDE metadata tables.

26. Pasting a drawing as a surface includes means to interpolate data using triangulation adjusted for contours, for increased accuracy. The triangulation is adjusted using the DEST algorithm.

25. The object model includes means to create a constrained triangulation.

24. Layers in maps created by the TIGER/Line import have been reordered so that point layers are above line layers and line layers are above area layers.

23. Importing a TIGER/Line data set supports TIGER/Line 2006 SE (Second Edition).

22. Exporting a drawing to an ArcSDE data source includes means to create and register a new coordinate system instead of using one of the coordinate systems that have already been registered in the data source.

21. The File - Export - Drawing command includes means to export drawing to an ArcSDE data source via ODBC or OLE DB. Exporting a drawing to an ArcSDE data source creates a table with geometry data, a table with attribute data, and adds records to the relevant ArcSDE metadata tables.

20. Importing a JPEG file reads XMP tags into component notes.

19. Importing a GeoTIFF file reads XMP tags into component notes.

18. Script components and add-in scripts can use IronPython. IronPython scripts intended to be used for active columns should only include the body for a single script function. To use IronPython in an add-in script, use a scripting engine called "IronPython.NET".

17. Importing a GeoTIFF file reads EXIF tags into component notes.

16. SQL engine supports a new data type for ArcSDE geometry data. This includes means to convert ArcSDE geometry to any other geometry type and vice versa.

15. Database Console includes means to import and link drawings from ArcSDE data sources. Coordinate systems are fetched from ArcSDE metadata.

14. Database Console recognizes ArcSDE data sources and lists available drawing layers.

13. The system remembers the last PostgreSQL data source successfully connected.

12. There are means to import and link tables from PostgreSQL data sources via the native PostgreSQL interface. Support for PostgreSQL requires the folder containing PostgreSQL client DLLs (LIBPQ.DLL plus any DLLs it depends on) to be referenced in the user's or system's PATH variable.

11. Image libraries and images linked from remote data sources share file watcher threads, to improve performance and decrease the amount of used memory.

10. Linking a drawing or table from a DB2 data source via OLE DB makes the resulting component read-only according to the detected table privileges.

9. Omitting a login name when connecting to a native DB2 data source uses integrated security.

8. There is a new set of transforms to build constrained Delaunay triangulation. Constrained Delaunay triangulation is Delaunay triangulation adjusted to include a set of segments supplied by the user. The "Constrained Triangulation Areas" transform triangulates a set of objects (all object types are allowed) and creates an area for each triangle in the resulting triangulation. The "Constrained Triangulation Lines" transform creates a line for each edge in the resulting triangulation. The "Constrained Triangulation" transform creates both areas and lines. See the new Help topic.

7. The object model includes means to import NetCDF files.

6. The File - Import - Surface command includes means to import NetCDF files.

5. The system remembers the last DB2 data source successfully connected.

4. The object model includes means to export and import tables to and from DB2 data sources.

3. There are means to import and link drawings from DB2 data sources. Reading data translates DB2 geometry to Geom values. Writing data translates Geom values back to DB2 geometry.

2. There are means to export tables to DB2 data sources via the native DB2 interface.

1. There are means to import and link tables from DB2 data sources via the native DB2 interface. Using the native DB2 interface is faster and more robust than accessing DB2 through intermediate database layers such as ODBC and OLE DB. Support for DB2 requires the folder containing DB2 client DLLs (DB2CLI.DLL plus any DLLs it depends on) be referenced in the user's or system's PATH variable.

DataSource

DataSourceColumnSet

Developing Applications

Drawing - Area of Interest

Example: Storing a Drawing in Manifold Spatial DBMS

Example: Storing an Image in Manifold Spatial DBMS

Example: Storing a Surface in Manifold Spatial DBMS

ExportDb2

ExportPostgreSql

ExportSqlServer

ImportDb2

ImportNetCdf

ImportPostgreSql

ImportSqlServer

Manifold Spatial DBMS Facilities

Manifold Spatial Extender for SQL Server

MapServerRenderFormat

NVIDIA CUDA

RecentDataSource

RecentDataSourceSet

Show Area of a Parcel in Acres

Spatial DBMS

Spatial DBMS Facilities

The Data Source Dialog

Transform - Constrained Triangulation

UserInterface

User Interface Scripting

UserInterfaceControl

UserInterfaceControlItem

UserInterfaceControlItemSet

UserInterfaceControlSet

UserInterfaceDialog

UserInterfaceDialogSet

What's New in 8