Manifold
System Release 7.00 Release Notes
Manifold
System Release 7.00 Release Notes
For a much easier to read and easier to understand list of the Top 100 highlights in Release 7.00 as voted by manifold.net marketing and engineering managers, see the 7.00 Highlights page.
This file contains the release notes used in beta testing. These provide a comprehensive (albeit raw) enumeration of all recorded changes made in the transition to the latest release. Think you have what it takes to be a beta tester? Imagine going through lists like this for months on end!
Release 7.00 Release Notes and Build History
Manifold System Release 7.00
15 May 2006
Following is a list of all items announced during the build history for 7.00.
Build 408 was the production release for 6.50.
Build 409
-------------------------------
1. The File - Link - Image command allows linking an image from a folder of
image files. Supported file formats are BMP, GIF, JPG, PNG, TGA and TIFF. An
image linked from a folder of image files is referred to as an "image library"
and individual image files are referred to as "tiles".
2. Linking an image library supports qualifying lengths of [X], [Y] and similar
escape sequences used in the filename mask. This allows decoding X and Y
coordinates in the filenames where these coordinates are glued together without
a separator, as in Ixxxyyy.JPG.
3. Linking an image library offers an option to treat the Y coordinates in the
names of tiles as increasing in either the top-down (option checked) or the
bottom-up (option unchecked, the default) direction.
4. Opening a project with an image library first tries to bind the image library
to a folder location relative to the project, then to an absolute folder
location. This allows moving files participating in an image library together
with the MAP file or files referring to them.
5. The Image object includes the new IsLibrary method, which can be used to
determine whether or not the image is an image library.
6. An image linked from a remote server can be converted to a native image using
the Image - Convert To command.
7. (Fix) The Info pane no longer sometimes clears itself after the user undoes
an operation which involves multiple drawings.
8. An image linked from a file or a remote server can be shared on an Enterprise
storage. Importing or linking such an image to a local project will re-establish
the connection to the relevant file or URL.
9. The clipping area used when projecting data with the "Clip coordinates"
option turned on is defined with the precision of 0.01 degree instead of 1
degree.
10. The memory footprint of the clipping algorithm used when projecting data
with the "Clip coordinates" option turned on has been decreased by a factor of
20 to 50, depending on the complexity of drawing objects being projected (more
complex objects correspond to greater memory savings percentage-wise).
11. (Fix) Linking data from an ADO .NET data source (eg, an XLS file) no longer
sometimes locks it.
12. Importing or linking data from a SQL Server, Oracle or similar data source
supports schemas.
13. Creating an instance of the MapServer object with an empty state string (eg,
for the first time in a session for a particular user) automatically goes to the
view named "Startup" (case does not matter), if such a view exists.
14. (Fix) Pasting a surface as a table no longer allows pasting aspect and slope
columns, which are not available in virtual tables for surfaces.
15. (Fix) The results of the Distance and DistanceEarth query functions no
longer depend on the order of their arguments, that is, Distance(a, b) always
returns the same result as Distance(b, a), same for DistanceEarth.
16. (Fix) Running a query with a spatial join no longer sometimes fails.
17. (Fix) Attempting to import a DBF file locked by another application (eg,
Excel) no longer creates a blank table.
18. (Fix) Rendering an elevation (component) with the "Label surface breaks"
display option turned on no longer sometimes produces lines and labels above and
below the elevation body.
19. Projecting lat/lon values between different datums takes into account datum
rotation factors.
20. A definition of a custom datum can specify datum rotation factors.
21. The Datum object includes means to control datum rotation factors.
22. (Fix) Altering properties of the Ellipsoid object bound to a Datum object no
longer fails to propagate changes to the Datum object.
23. (Fix) Copying a record from a table returned by a query and pasting the
result in the Project pane no longer creates a component with a blank name.
24. (Fix) Invoking the context menu for a table column disables the Identity
command if the column can not be an identity column.
25. (Fix) Splitting a complex area with a line no longer sometimes attaches
patches of the line to the results of the split.
26. (Fix) Subtracting a complex area from another area no longer sometimes fails
to subtract parts of the area.
27. (Fix) Snapping to a map layer whose coordinate system is equivalent to that
of the map with the exception of the datum no longer sometimes snaps to a wrong
location.
28. Queries include means to create a new line geom.
29. Queries include means to add a coordinate to a line geom.
30. (Fix) Downloading tracks from Garmin no longer sometimes glues them
together.
31. (Fix) Importing a drawing from an SDTS transfer no longer ignores currency
columns.
32. (Fix) Attempting to load thematic formatting into a Format object not bound
to a column throws an error instead of rendering the object invalid.
33. Checking in a shared component no longer requires permissions to delete
(drop) tables on the database server.
34. Linking a table from an XLS file via ODBC, OLE DB or ADO .NET OLE DB in
read-only mode no longer locks the file.
35. (Fix) Importing a drawing from a SHP file on a system with non-English
regional options no longer sometimes loses decimal comma in floating-point
values.
36. (Fix) Adding new columns to a drawing as part of a transform no longer adds
columns in the reverse order.
37. (Fix) The HeightAvg, HeightMax, HeightMin and several other query functions
working with surfaces no longer mirror the passed Y coordinate.
38. (Fix) Doing a topology overlay correctly transfers columns whose transfer
rules refer to intrinsic columns (eg, columns which have been set to transfer
proportionally to Area (I)).
39. The TOP and SKIP quantifiers used in queries can be parameterized.
40. The query engine prohibits enclosing date literals in quotes (",
Jet-compatible syntax) or apostrophes (', ANSI-compatible syntax), to avoid
confusion with string literals. Use hashes (#).
41. (Fix) Selecting objects by running a query which involves a comparison of
the values in the ID column with a literal value (eg, SELECT * FROM D WHERE
ID=1) no longer sometimes skips area objects with more than one branch.
42. (Fix) The CenterCorrelation method of the RecordSet object no longer returns
a wrong value.
43. (Fix) Completing a word when editing a query no longer occasionally leaves
the cursor in a wrong position.
44. (Fix) Opening a query window with the autocompletion services turned off no
longer permanently disables autocompletion services for this window.
45. (Fix) Pasting text into a comments, query or script window no longer
requires two undo steps for a complete undo.
46. (Fix) Entering text in overtype mode in a comments, query or script window
no longer sometimes erases all text when undone.
47. Highlighting the syntax of a script performs significantly faster.
48. The CREATE VIEW query statement allows creating a query referring to a table
or column that does not yet exist.
49. The new CREATE DRAWING query statement allows creating a new drawing with a
given set of columns.
50. (Fix) Copying and pasting a table bound to a drawing no longer resets
transfer rules referring to intrinsic columns.
51. (Fix) Attempting to set the transfer rules of a non-native column (eg, an
intrinsic column) using a script fails.
52. (Fix) Pasting a drawing as a profile projects data to the coordinate system
of the parent surface.
53. (Fix) Importing a multi-channel BIL file no longer locks the file after the
import completes.
54. (Fix) Importing Z coordinates from a DWG file no longer sometimes produces
garbage data.
55. The TIGER/Line import supports TIGER/Line 2004 data.
56. Importing a surface from an ERS file named XXX.ERS tries to obtain data from
the XXX.DAT file in case the XXX file can not be found.
57. (Fix) Importing a drawing from an E00 file with more than one attribute
table no longer sometimes scrambles column data.
58. (Fix) Importing an image from a NITF file no longer sometimes creates a
blank comments component.
59. Attempting to add a coordinate to a Geom object for a point using a script
fails with a descriptive error message.
60. (Fix) Attempting to add a coordinate to a Geom object created from a WKT
using a script no longer sometimes does nothing.
61. (Fix) Renaming a drawing no longer fails to update the drawing combo in GPS
Console.
62. It is possible to make a Geom object created using a script invalid, as long
as the object does not represent the metric of any real drawing object or label.
For example, it is possible to delete the last point in a branch or delete the
last branch of such a Geom object. This corrects the strange situation that
existed when a standalone Geom object was invalid at creation time, but could no
longer become invalid after it was made valid.
63. Exporting a drawing as a MIF sets the outline color of each exported area to
the area border foreground color.
64. Dropdown well windows used in the Format toolbar and in other toolbars
include buttons to scroll all the way up or down.
65. Importing a drawing with formatting data from a MIF file has been optimized
to work significantly faster.
66. Queries include means to compute ellipsoidal lengths and areas.
67. (Fix) Creating a surface by pasting a drawing or a table no longer offsets
interpolated data by half-pixel.
68. (Fix) Using one of the interpolation functions in the Surface - Transform
dialog no longer offsets interpolated data by half-pixel.
69. Spatial indices used for vector data sets better optimize themselves after
deletions.
70. (Fix) Joining areas using the Union transform or the Dissolve tool no longer
sometimes loses parts of complex areas.
71. (Fix) Doing a topology overlay no longer sometimes loses parts of complex
areas.
72. (Fix) Clicking into an object no longer sometimes displays a (harmless)
error message if one or more add-in panes are installed.
73. Moving the focus out of a comments, query or script window fades the
background color of selected text.
74. (Fix) Running a script in a read-only MAP file no longer makes the script
editable after it completes.
75. (Fix) Previews of legend elements are no longer being cut at 256 pixels.
76. (Fix) Deleting a relation in a table no longer sometimes fails to propagate
changes to the related table.
77. The VALUES query statement can return multiple records.
78. The OGC WMS client automatically corrects several types of malformed URLs
returned by the server.
Build 410
-------------------------------
79. Attempting to delete a table bound to a drawing using "DROP TABLE x" fails
with a descriptive error message.
80. The new DROP DRAWING query statement allows deleting an existing drawing.
81. (Fix) Comments, query and script windows no longer ignore bold, italic and
similar attributes of the relevant font entry in Tools - Options, Fonts.
82. Icon buttons similar to the refresh button in the Link TerraServer Data
dialog adjust their look according to the current Windows theme.
83. (Fix) Importing an image from a BMP, GIF, JPEG, PCX, PNG or TGA file
accompanied by a world file no longer leaks a small amount of memory.
84. The File - Export - Table, File - Import - Table, File - Link - Table
commands and the Database Console dialog allow exchanging data with Oracle data
sources via the native Oracle interface (Oracle Call Interface or OCI). Using
the native interface provides for better performance and allows using features
not exposed through generic database interfaces, such as ODBC, OLE DB and ADO
.NET.
85. Exchanging data with Oracle data sources via the native Oracle interface
maps geometry columns to SDO_GEOMETRY data. SDO_GEOMETRY values representing
collections of geometric entities are not supported.
86. There is a new cylindrical coordinate system: Gall.
87. There is a new azimuthal coordinate system: Peirce. The definition of the
projection in common use does not include formulae for the inverse
transformation, so projecting from Peirce to lat/lon uses iterative
approximations and can lose precision.
88. There are two new pseudocylindrical coordinate systems: Guyou and Van der
Grinten IV. The definitions of the projections in common use do not include
formulae for the inverse transformations, so projecting from either of the
projections to lat/lon uses iterative approximations and can lose precision.
89. There is a new coordinate system preset for Mississippi Transverse Mercator.
90. The results of a coordinate system transform are forced to stay finite. This
allows working with maps containing layers with locations which can not be
represented in the coordinate system of the map (eg, working with a Mercator map
containing a lat/lon drawing of Antarctic region with objects touching the
latitude of -90, which would have been projected to infinity).
91. There is a new query function to rotate a geom near a given location.
92. The LabelSet object includes the Box property.
93. Attempting to connect to a GPS receiver unit using the Test button in the
GPS Receiver Properties dialog outputs the list of recognized NMEA tags for an
NMEA connection and a list of recognized subprotocols together with their
versions for a GARMIN connection.
94. (Fix) GPS Console no longer occasionally fails to download or upload data
from or to a GPS receiver unit connected via the GARMIN interface.
95. Attempting to run a query with an ambiguous parameter name (eg, selecting
from a table T with a column A: PARAMETERS A INT; SELECT * FROM T WHERE A=A)
fails with an error message.
96. (Fix) Running a query with a complex join condition no longer sometimes
fails to return results.
97. Importing a JPEG image with EXIF tags places tags into component notes.
98. Importing a JPEG image with an orientation EXIF tag (typically produced by
digital cameras) rotates and flips the image as necessary.
99. (Fix) Importing Z data from a DWG drawing no longer applies the Z scale of a
block to the Z coordinate of a block insertion point.
100. Importing a DLG 100K file automatically handles inconsistent line ends.
101. (Fix) Loading a PRJ file with an unknown datum into a coordinate system
dialog no longer sets the datum to the first choice in the datum combo box
(usually, Adindan).
102. Loading a coordinate system from a PRJ file recognizes several new
variations of datum names.
103. (Fix) Importing a E00 file no longer sometimes fails to import column data.
104. Importing a E00 file imports auxiliary attribute tables.
105. Importing a E00 file imports auxiliary label sets.
106. The ADF import supports importing vector data sets. Importing a vector data
set displays a dialog with the list of columns to import and other import
options. The "Compose areas" option (off by default) combines line objects into
area objects, provided the ADF file set contains relevant data. The "Import
ticks" option (off by default) imports tick marks similar to those in E00 files.
107. The ADF import supports importing TINs. Importing a TIN displays a dialog
with import options. The "Import points" option (off by default) creates a
drawing of points and stores the height of each point in a column. The "Import
triangles" option (off by default) creates a drawing of triangles. The "Import
surface" option (on by default) creates a surface. The dimensions of the surface
are specified by the user.
108. The ImportAdf object includes means to access import properties.
109. The File - Link - Image command allows linking an image from the Google
Maps server.
The Link Google Maps Data dialog includes means to specify a theme, which
defines the scheme of structuring web requests as well as the base URL. The base
URL can be overridden using the "Use custom server URL" option. Currently, there
is only one theme named "Vector Map".
The Refresh button to the right of the Server text box tries to connect to the
URL specified in that box and reports progress in the text field just above the
"Cache data between sessions" option.
The Scale combo controls the maximum allowed zoom scale. The default value of
the maximum scale is 1 meter per pixel, the same as for TerraServer. The larger
the value of the maximum scale, the smaller the linked image component.
The Longitude and Latitude text boxes specify the bounding box of the resulting
image, in degrees. By default, the bounding box is set to cover the area
displayed in the active component window. If there is no active window, or if
the active window does not display a geographic area (say, a table window), the
bounding box is set to cover the area of the US.
The "Cache data between sessions" option (on by default) toggles the use of
permanent cache.
The Proxy button invokes the Proxy dialog, which allows customizing proxy server
options.
To link an image from the Google Maps server, invoke File - Link - Image, Google
Maps Server, press the Refresh button to the right of the Server text box to
make sure the server can be reached, and press the OK button. Then open the
resulting image component and try zooming in.
An image linked from the Google Maps server is rendered using the code for an
image library. Thus, rendering an area which has not yet been downloaded from
the server at the correct scale will attempt to use pixels downloaded for this
area at less detailed scales, which is a big win (and a wishlist item for images
linked from OGC WMS servers and TerraServer).
110. The Image object includes means to check whether or not the image component
is linked from the Google Maps server.
111. Buttons hosting dropdown well windows found in the Format toolbar and in
other places adjust their look according to the current Windows theme.
112. (Fix) Using mixed-mode coordinate entry no longer produces rendering
artifacts.
113. The tree of database objects in the Database Console dialog can be filtered
to only include objects whose names contain a particular sequence of characters
by typing into the text box right above the tree. This is particularly helpful
when working with data sources with lots of objects, such as SQL Server or
Oracle data sources.
114. Connecting to an Oracle data source via the native Oracle interface in
Database Console displays tables with one or more SDO_GEOMETRY column as
drawings and allows importing and linking them.
115. Importing or linking a drawing from an Oracle data source using Database
Console preserves coordinate system data.
116. Right clicking a component linked from an external data source in the
Project pane, and invoking the Open Data Source command opens Database Console
and connects to the component data source. Opening a component linked from an
external data source in its own window, and invoking the Open Data Source
command in the component menu (eg, Drawing - Open Data Source for a drawing)
does the same.
117. The File - Export - Drawing command allows exporting a drawing to an Oracle
data source using the native Oracle interface.
The Server text box specifies the server to connect to. The User Name and
Password text boxes specify the login info to use. The Connect button
establishes the connection to the server and enables the remaining controls.
The Name text box specifies the name of the new table to create on the server.
The Columns list controls the columns to export. By default, the system exports
all columns except intrinsics.
The Projection field contains the name of the projection to use. The projection
is selected from the list of projections supported by the server. The Browse
button to the right of the Projection field allows customizing the default
projection chosen by the system.
Build 411
-------------------------------
118. The Link Google Data dialog allows using a "Satellite Image" theme. The
default scale for the "Satellite Image" theme is 10 meters, which is the current
maximum supported by Google Maps.
119. Rendering an image library uses significantly less memory. This makes it
easier to use large image libraries together with other large components.
120. The object model includes means to project components.
121. Exporting a drawing to an Oracle database includes an option to create a
spatial index for the drawing (on by default).
122. (Fix) Exporting a surface interpolated from a drawing or table as an ESRI
ASCII Grid file no longer sometimes exports wrong values of the local offset and
local scale coordinate system parameters.
123. (Fix) Attempting to register an image or a surface using a target set of
control points positioned along a horizontal line no longer sometimes fails.
124. (Fix) Altering the current coordinate system of a component updates the
scalebar, if it is shown in a component window.
125. (Fix) Resizing a table column no longer sometimes fails to update the
horizontal scrollbar in the table window.
126. An image library can be exported to a file.
127. An image library can be unlinked or converted to another image type using
Image - Convert To.
128. An image library can be shared on an Enterprise storage.
129. An image linked from Google Maps can be exported to a file.
130. An image linked from Google Maps can be unlinked or converted to another
image type using Image - Convert To.
131. An image linked from Google Maps can be shared on an Enterprise storage.
132. Importing or linking a table from a CSV file no longer requires having
write access to the folder containing the CSV file to customize import options.
133. (Fix) Importing or linking a table from a CSV file using the space
character as the delimiter no longer fails.
134. The Import CSV File dialog includes means to customize the decimal
delimiter character and the text qualifier character.
135. The Import CSV File dialog automatically suggests values for the delimiter,
decimal delimiter and quote qualifier characters based on the first lines of the
CSV file.
136. The character set combo in the Import CSV File dialog is replaced with the
"Force ANSI character set" checkbox. If the option is unchecked (the default),
text data is interpreted using the locale of the current user. If the option is
checked, text data is interpreted as being in the ANSI code page.
137. The Import CSV File dialog includes means to preview the effect of the
selected import options.
138. The Import CSV File dialog includes the new "Import all fields as text"
option. By default, the option is turned off.
139. (Fix) Attempting to import or link a drawing, an image or a surface from a
DBF file no longer fails.
140. The ImportCsv object includes means to set the list delimiter, decimal
delimiter and text qualifier characters and other import options.
141. The Query object includes means to access the ANSI-compatible syntax
property.
142. (Fix) The Columns property of the ImportGdf object has been renamed to
Modules.
143. (Fix) The Columns property of the ImportSdts object has been renamed to
Modules.
144. (Fix) The Columns property of the ImportMapBase object has been renamed to
Modules.
145. (Fix) Returning a ConverterItemSet object from an export or import object
no longer sometimes leaks a small amount of memory.
146. There is a new supported measurement unit: Modified American Foot.
147. The Layer object includes the Order property, which allows accessing the
layer position in the display stack.
148. Images linked from Google Maps support downloading image levels via Image -
Download.
149. Downloading levels of an image linked from TerraServer via Image - Download
no longer stops when some tiles can not be retrieved.
Build 412
-------------------------------
150. Images linked from Google Maps servers use the Manifold Image Server
interface. The names of all dialogs, controls and menu commands have been
adjusted accordingly.
151. The Database Console dialog displays images stored on an Oracle database,
if connected using the native Oracle interface, and allows importing and linking
them.
152. An image linked from an Oracle database can be exported to a file.
153. An image linked from an Oracle database can be unlinked or converted to
another image type using Image - Convert To.
154. An image linked from an Oracle database can be shared on an Enterprise
storage.
155. The Image object includes means to check whether or not the image component
is linked from a database (eg, an Oracle database).
156. The "Derive coordinate systems from filenames" radio button in the Link
Image Library dialog has been renamed to "Arrange images using filenames". The
"Load coordinate systems from coordinate system definition files" radio button
has been renamed to "Georegister using accompanying files". The help text under
the Mask text box has been adjusted to provide several example masks.
157. The Pixel object includes the writeable Visible property, which supercedes
the IsMissing and IsInvisible methods of the same object.
158. The Object, Label, Pixel and several other objects include the writeable
Selected property, which supercede the IsSelected methods of the relevant
objects.
159. The Record object includes the IsMasked method which determines whether or
not a record belongs to a particular saved selection.
160. (Fix) Transferring data using the Median transfer rule no longer works
incorrectly under certain circumstances.
161. Queries include means to translate binary data to text format and vice
versa. This is useful for storing binary data in, say, DBF files which do not
support binary columns.
Build 413
-------------------------------
162. (Fix) Rendering an IMS image which includes a portion of the image linked
from TerraServer waits until the system fully downloads the portion of that
image from the Internet.
163. The "Theme" caption in the Link Manifold Image Server Data dialog has been
changed to "Server". The former "Server" caption has been changed to "URL".
164. Double clicking a node in the tree of database objects in Database Console
encloses the name of the object inserted into the query text box with
connection-specific quote characters.
165. There is a new Help - Web - Community menu item which opens the Manifold
Community Site in the new browser instance.
166. (Fix) Attempting to link an image from a remote server covering the area
displayed in an active component window computes the lat/lon coordinates of the
area using the datum of the active component.
167. The ECW / JPEG2000 code has been synchronized with the latest version of
the ECW / JPEG2000 SDK published by ER Mapper.
168. Invoking the Database Console dialog postpones connecting to the last used
data source until the user clicks the Refresh toolbar button.
169. (Fix) Losing a connection in the Database Console dialog no longer fails to
disable the Run (Query) toolbar button.
170. Losing a connection in the Database Console dialog disables the object tree
and the query text box.
171. The Database Console dialog has been redesigned to place the object tree
and the query text box on top of each other instead of side by side. The filter
text box has been supplied with a label.
172. The IMS config.txt file can include options for proxy connection info and
file locations as follows:
configurationFolder - The location of the Configuration folder, as given in
Tools - Options, File Locations.
dataCacheFolder - The location of the Data Cache folder, as given in Tools -
Options, File Locations.
datumGridsFolder - The location of the Datum Grids folder, as given in Tools -
Options, File Locations.
geocodingDatabaseFolder - The location of the Geocoding Database folder, as
given in Tools - Options, File Locations.
geocodingExtensionsFolder - The location of the Geocoding Extensions folder, as
given in Tools - Options, File Locations.
mrSidDecodeUtilityPath - The path to the MrSID Decode utility, as given in Tools
- Options, File Locations.
mrSidInfoUtilityPath - The path to the MrSID Info utility, as given in Tools -
Options, File Locations.
proxy - Set to "true" if network connections require the use of a proxy server,
set to "false" otherwise.
proxyAddress - Proxy server address, eg, "http://netproxy:8080".
proxyPassword - Password used to login onto the proxy server.
proxyUser - User name used to login onto the proxy server.
173. The File - Export - Web Page dialog includes an option to save proxy
connection info and file locations in a config file. By default, the option is
turned off, to minimize the risk of leaking sensitive data such as passwords or
physical paths used on the system. In some cases, such as when the exported web
page uses components linked from remote servers, it might be necessary to turn
the option on to supply these components with data required for correct
function.
174. Attempting to export a web page with an image linked from a remote server
or a map that includes such an image as a layer displays a warning message in
case the user has chosen not to save proxy connection info and file locations
into the config file.
175. The status readout for an image stored on an Oracle database in the
database object tree in Database Console includes the dimensions of the image,
the number of channels and the data type used for image pixels.
176. The MapServer object includes means to compute the bounding box of all data
in a served component.
177. Attempting to export a drawing with more than one variable-length column to
an Oracle database fails with a message that lists the variable-length columns
and advises to convert one or more of these columns to fixed-length types, or
uncheck them in the list of exported columns. Oracle tables can not have more
than one variable-length column.
178. The code importing or linking images from an Oracle database has been
extended to support indexed color images and images stored with channel
interleaving.
179. (Fix) Add-in scripts no longer fail to run, sometimes causing a crash.
180. Zooming into an image linked from an OGC WMS server makes use of data in
the levels less detailed than the one queried, to quickly render the queried
area using whatever data is currently available and progressively update the
display as new data comes up.
181. Zooming into an image linked from TerraServer makes use of data in the
levels less detailed than the one queried, to quickly render the queried area
using whatever data is currently available and progressively update the display
as new data comes up.
182. Importing a JPEG image with EXIF tags recognizes EXIF tag directories
written by major camera vendors.
183. The File - Import - Image dialog includes means to import DNG files (an
Adobe variation of TIFF for use with digital photography).
184. (Fix) Importing TIGER/Line 2004 files no longer sometimes fails when
composing areas.
185. (Fix) Exporting a large drawing to an Oracle database no longer sometimes
runs out of memory due to a memory leak.
186. (Fix) Failing to export a drawing to an Oracle database, eg, due to a loss
of network connectivity, rolls back all changes made to the database.
187. The installation package includes a Manifold Image Server module which
connects to a Manifold IMS website.
188. The File - Export - Web Page dialog includes an option to export a page
which can be used by the Manifold Image Server module for Manifold IMS websites.
By default, the option is turned off.
189. (Fix) Exporting a table or drawing to an Oracle database no longer fails if
the exported rowset includes a variable-length column and this column is not the
last one.
190. Rotating an image or a surface to a multiple of 90 degrees performs
significantly faster.
191. (Fix) Activating Manifold from the command line using both a serial number
and an activation key no longer displays the Activation dialog.
192. Activating Manifold or a Manifold extension from the command line exits
application after the activation, to facilitate unattended installation
scenarios.
193. (Fix) A web page using an image linked from a Manifold Image Server no
longer sometimes displays nothing.
Build 414
-------------------------------
194. Connecting to a remote data source using one of the Oracle-specific dialogs
engages the "busy" indicator in the status bar and replaces the current cursor
with the system "busy" cursor for the duration of the data exchange with the
data source.
195. (Fix) The projection selection dialog used when uploading data to Oracle
data sources no longer fails to trim the name of the Manifold projection to
exclude system data.
196. Linking an image from a Manifold Image Server displays the dimensions of
the image component to be created.
197. Oracle-specific dialogs remember the last used server and login name.
198. (Fix) Image tiles downloaded from Google servers are no longer saved with
the wrong extension (JPG instead of PNG).
199. Dropping a linked image from the Project pane into a map with an
incompatible coordinate system displays a warning message.
200. Creating a map with two or more linked images with incompatible coordinate
systems displays a warning message.
201. (Fix) Sorting an intrinsic column or running a transform involving an
intrinsic column no longer sometimes crashes.
202. (Fix) Importing block data from a DWG file no longer incorrectly scales and
shifts Z coordinates.
203. (Fix) Importing a MapInfo TAB file with long column names (longer than
allowed by the format of the accompanying DAT file) no longer works incorrectly
when some columns reduce to the same short names.
204. (Fix) Turning off the proxy server in dialogs supporting use of proxy
servers no longer continues to connect using the old proxy connection info until
Manifold is restarted.
205. (Fix) Connecting to a Manifold IS (Image Server) built on a Manifold IMS
web site no longer fails to work if the dimensions of an image served by the
server at the highest available scale exceed 4 billion pixels in any direction.
Build 415
-------------------------------
206. (Fix) Use of image libraries or images linked from image servers no longer
risks corruption of other components. A special build has been issued out of
sequence to correct this potentially very serious problem.
Build 416
-------------------------------
207. (Fix) Exporting a drawing to an Oracle database no longer sometimes leaks
memory if the coordinate system of the drawing differs from lat/lon.
208. (Fix) Canceling a lengthy copy operation no longer sometimes crashes.
209. Database Console allows importing as a surface a channel of an image stored
in an Oracle database.
210. (Fix) Working with more than one MAP file in an interactive session of
Manifold using a script no longer sometimes crashes (importing a component from
another MAP file into the active MAP file is safe).
211. (Fix) Hosting more than one web site in the same OS process no longer
sometimes crashes.
212. (Fix) Creating a map using more than one image library or image linked from
a remote server no longer wrongly warns of incompatible coordinate systems if
that is not the case.
213. Linking a drawing from a table or query using a geometry column replaces
the metric of objects that have invalid or missing geometry data with a single
(0:0) coordinate, effectively treating each such object as if it has been a
point in the origin of the coordinate system of the drawing. "Multi-point"
geometry values generated by AllCoords and several other query functions are
handled similarly. The IDs of the first ten objects with a replaced metric are
logged into the History pane. This captures invalid objects into a known,
presumably "safe" location.
214. Linked drawings support altering column data.
215. Linked drawings support altering geometry data. This includes all visual
editing tools as well.
216. Drawings have been made significantly more robust with respect to bugs in
imports and transforms.
217. Linked drawings and labels bound to linked drawings no longer persist the
metric of drawing objects and labels into the MAP file. This saves space and
increases the performance of saves.
218. The default value of the "Refresh linked components after opening file"
option in Tools - Options, Miscellaneous has been changed to "on", to populate
linked drawings after opening a MAP file and to re-populate them after saving a
MAP file.
219. Names of linked components that failed to refresh in the process of opening
a MAP file are logged into the History pane.
220. Linked drawings support adding or removing objects, provided the data
source supports adding or removing table records. For example, it is possible to
add or remove objects in a drawing linked from a table with a geometry column in
the same MAP file, but it is not possible to add or remove objects in a drawing
linked from a SELECT query that references the same table.
221. (Fix) The Normalize Topology and Decompose to Triangles transforms no
longer sometimes desync the operated drawing with its table (which usually
caused a crash immediately after - rare, but possible).
222. (Fix) Saving a blank drawing or labels component no longer loses
established point rotation and area border formatting.
223. (Fix) Running a drawing transform on objects belonging to several different
drawings no longer sometimes fails.
224. (Fix) A table window no longer allows removing the last column from a
standalone table.
225. (Fix) Hiding or showing table columns no longer fails to enable or disable
controls in the Transform toolbar (which list currently shown columns).
226. Error messages thrown by OLE DB facilities have been made more
user-friendly.
227. Component context menus in the Project pane now include a Refresh Data
command which refreshes the content of linked components.
228. (Fix) The Topology Overlay dialog no longer sometimes lists fake saved
selections with empty names.
229. The File - Export - Image dialog includes means to export an image to an
Oracle database. If the coordinate system of the image is not supported by
Oracle, the image will be automatically projected to the closest coordinate
system supported by Oracle.
230. The name of an image exported to an Oracle database can follow one of the
below schemas:
RDT
RDT.RASTERID
RASTERTABLE.RDT
RASTERTABLE.RDT.RASTERID
RASTERTABLE.RASTERCOLUMN.RDT
RASTERTABLE.RASTERCOLUMN.RDT.RASTERID
RDT is the name of the raster definition table, RASTERID is the ID of the raster
in the raster definition table (an integer value), RASTERTABLE is the name of
the raster reference table, and RASTERCOLUMN is the name of the column in the
raster reference table.
In addition to recognizing the above schemas, the export dialog also provides
means to edit all parts of the image name explicitly.
231. (Fix) Removing a component using a script no longer allows removing a
shared component that is checked out. Attempting to remove a checked in
component which has one or more dependent components that are checked out fails
as well.
232. (Fix) Removing a component using a script no longer sometimes fails to
remove all dependent components in certain cases of complex dependencies.
233. The Tools - Options, User Interface page includes the new "Restrict mouse
wheel to only operate over focused window" option, which protects against
accidentally changing the current scale via the scale combo box in the
Navigation toolbar and performing other unintentional actions using the mouse
wheel. By default, the option is turned on.
234. The BatchUpdates property of the Document object which increases the
performance of scripts in bulk update scenarios works for all MAP files, not
just the active MAP file.
235. Linking a drawing using coordinate columns creates explicit query
components and links these.
236. Linking a drawing using coordinate columns allow supplying a column used to
order records when creating lines.
237. Attempting to relink a linked drawing disables linking using coordinate
columns.
238. Opening a MAP file with linked drawings created by 6.50 or earlier versions
of Manifold unlinks these drawings. The names of the unlinked drawings are
logged into the History pane.
239. (Fix) Deleting the last layer of a map no longer sometimes crashes.
240. Columns in a linked table support transfer rules.
241. A linked drawing or a shared drawing that is not checked out itself but has
a checked out table can be the target of a spatial overlay.
242. (Fix) Running the Full Width or a similar alignment command in a map window
no longer excludes shared drawings that are not checked out from bounding box
computations.
243. Running an alignment command in a map window performs significantly faster.
244. Attempting to reproject a linked drawing reloads its data from the data
source.
245. (Fix) Copying data into the Clipboard no longer sometimes fails to
overwrite the existing contents of the Clipboard and instead adds to it.
246. (Fix) The IntersectionPoint query function which returns a collection of
intersection points of two lines no longer sometimes returns an extra point.
247. (Fix) Converting coordinates between datums using a custom datum
transformation no longer sometimes loses precision.
248. (Fix) Decomposing a complex area to convex parts using a script no longer
sometimes fails.
249. Exporting data to Oracle matches State Plane coordinate systems to their
Oracle equivalents despite the small differences in the coordinate system
definitions caused by varying levels of precision.
250. (Fix) The CheckContains and similar methods of the Geom object no longer
sometimes fail.
251. The Object object includes means to retrieve the record associated with the
drawing object. The Record object includes means to retrieve the drawing object
associated with the record.
252. (Fix) Importing data from a DXF file no longer incorrectly scales and
shifts Z coordinates in blocks.
253. (Fix) Importing data from a DXF file no longer aggregates Z coordinates for
some multi-point entities into a single value.
254. (Fix) Importing a TIGER/Line 2004 SE data set no longer sometimes imports
garbage column values due to a file reading skew.
255. TIGER/Line import supports TIGER/Line 2005 data sets.
256. Importing a MIF or TAB file translates "logical" columns to boolean.
257. Exporting a drawing to a MIF file exports boolean columns as "logical".
258. (Fix) Importing or linking an ECW file no longer sometimes fails if the
file does not contain coordinate system data.
259. (Fix) Linking an image from an OGC WMS server for which the capabilities
document references one or more external schemas no longer fails for some
configurations of the proxy server connection.
260. (Fix) Exporting an image to a ECW file no longer sometimes loses coordinate
system data.
261. Rendering an image linked from a remote server first fetches tiles closest
to the center of the visible area of the image and then proceeds to the edges of
the visible area.
262. The scale limit for satellite images linked from Google Maps has been
raised from 10 meters to 1 meter.
263. The code doing progressive rendering of image libraries and images linked
from remote servers has been optimized to reduce flicker.
264. The Link Image Library dialog includes the new "Scan subfolders" option. If
the option is turned on (the default), the image library will use files in the
specified folder and all its subfolders. If the option is turned off, the image
library will use files in the specified folder, but not in the subfolders.
265. The Link Image Library dialog includes the new "Automatically save
intermediate levels" option. If the option is turned on (the default), the image
library will save autogenerated tiles for intermediate image levels into the
folder with other image tiles, which greatly improves performance. If the option
is turned off, the image library will try to keep autogenerated tiles in RAM and
then, when the amount of available RAM becomes less than a pre-defined safety
level, throw them away in order to regenerate them again on demand.
266. The memory footprint of image libraries has been significantly reduced.
267. (Fix) Attempting to edit the name of a column in the Table Design dialog
and scrolling the column list automatically completes the editing.
Build 417
-------------------------------
268. Opening a MAP file with linked drawings created by 6.50 or earlier versions
of Manifold relinks drawings linked using a geometry column, provided their data
sources are reachable, and unlinks drawings linked using coordinate columns. The
names of all altered components are logged into the History pane.
269. (Fix) Performing lengthy operations, such as file imports, simultaneously
from more than one thread no longer sometimes fails due to a race condition in
progress tracking logic.
270. (Fix) Attempting to reproject a compressed image, an image library, or an
image linked from a remote server or database displays an error message instead
of crashing.
271. The Drawing object includes means to check whether or not the drawing
supports adding or removing objects or altering their metric.
272. The list of columns in the Oracle Data Source dialog used to export a
drawing to an Oracle database does not include the ID column and the Geom(I)
column, which are always exported.
273. (Fix) Removing a drawing referenced by a query immediately after running
the query no longer sometimes crashes.
274. (Fix) Removing a component referenced by a query immediately after running
the query no longer sometimes crashes when the component participates in a map
that is currently opened.
275. Opening, closing or saving the active MAP file logs operation status into
the History pane.
276. Linking a drawing from data in the same MAP file allows using a table
linked from another data source, to create cascading links. Refreshing data in a
drawing linked from another linked table in the same MAP file does not
automatically refresh data in the linked table. Circular links are resolved
automatically.
277. (Fix) Loading a MAP file with a linked table no longer fails to refresh
data in the table when the "Refresh linked components after opening file" option
is turned on.
278. Loading a MAP file with linked components using a script refreshes data
according to the value of the "Refresh linked components after opening file"
option.
279. Loading a MAP file with linked components in the context of a web site
refreshes data according to the value of the "refreshLinksOnOpen" config file
option.
280. (Fix) Renaming a column in a linked table no longer adds a new column into
a table window.
281. The Document object includes means to refresh all linked components.
282. The Document object includes means to check whether or not it is the active
document.
283. Exporting a table to an external data source makes all exported columns
except the identity column (ID) nullable.
284. (Fix) Refreshing data in a linked drawing no longer fails when one of the
labels components bound to the drawing is opened and contains a primary selected
label.
285. (Fix) Copying a large amount of image or surface pixels no longer fails to
put copied data into the Clipboard if the operating system can not convert
copied data into a bitmap, due to the bitmap size, to allow pasting data into
Microsoft Paint or other applications.
286. (Fix) Attempting to load or save a mask or channel of a surface or
attempting to alter the selection of a surface using one of the Edit - Modify
Selection commands no longer crashes if invoked from a map window.
287. The PixelSet object includes means to add or remove pixels for objects
representing the selection or a saved selection in an image or surface
component.
288. The Add, Remove and RemoveAll method of a RecordSet object representing the
selection or a saved selection in a table component will add or remove records
to or from the selection or saved selection.
289. Removing records in the RecordSet object representing all records in a
table bound to a drawing no longer fails with an error message and instead
removes relevant drawing objects.
290. (Fix) Altering a saved selection of a component using a script no longer
fails to update component windows.
291. (Fix) Adding a theme layer to a map using a script no longer fails.
292. The component objects include means to access the background color.
293. (Fix) Adding or removing labels from a labels component bound to a drawing
using a script no longer fails.
294. (Fix) Pasting text data from Notepad or another Windows application into a
table no longer treats the first row as if it contains column names even if the
relevant option in the paste dialog is turned off.
295. (Fix) Pasting text data from Notepad or another Windows application into a
table no longer sometimes inserts an extra column populated with end-of-line
characters.
296. Refreshing data of a linked drawing fails gracefully in case of a
connection error (eg, caused by a network failure).
297. (Fix) The query engine no longer sometimes fails to compare text data due
to a mis-optimization.
298. (Fix) Unlinking a linked table no longer loses data.
299. (Fix) Importing a drawing from a table data source no longer sometimes
loses data in the imported data table.
300. (Fix) Attempting to import or link a drawing from a native Oracle data
source no longer sometimes corrupts data on the data source.
301. A linked table allows adding or paste-appending a new column, renaming an
existing column, and changing the type of an existing column. This applies to
both standalone linked tables and tables bound to linked drawings.
302. It is possible to change the design of a linked table. This applies to both
standalone linked tables and tables bound to linked drawings.
303. It is possible to geocode records in a linked table. This applies to both
standalone linked tables and tables bound to linked drawings.
304. Exporting a drawing to a native Oracle data source postpones creating a
spatial index until after all drawing objects are uploaded. If the index
creation fails, all uploaded data stays in the database.
305. Exporting a drawing to a native Oracle data source creates a sequence
object and a trigger to automatically fill the ID column when adding new
objects.
306. (Fix) Accessing date-and-time data via the native Oracle interface no
longer crashes.
307. (Fix) Exporting a drawing to a native Oracle data source no longer fails
with an "invalid identifier" error message on older versions of Oracle.
308. Exporting a drawing to a native Oracle data source uses far less memory
than before and is generally faster.
309. Failing to update a component linked from an external table reports
detailed error data returned by the data source.
310. (Fix) The geocoding engine no longer sometimes fails to use geocoding
extensions if neither Manifold Geocoding Data nor MapPoint (any edition) is
installed.
311. (Fix) Importing a drawing from a DGN file no longer sometimes fails to
close spline shapes and compute correct coordinates for certain cases of complex
linear and spline shapes. Most splines are currently imported as straight lines.
312. Image libraries georegistering tiles using accompanying files recognize
shifts and scales stored in world files.
313. Image libraries georegistering tiles using accompanying files recognize
coordinate system data stored in GeoTIFF files.
314. Image libraries support ECW tiles. Image libraries georegistering tiles
using accompanying files recognize coordinate system data used in ECW files.
315. There is a new Image - Create Index Drawing command that creates an index
drawing for an image library.
316. The Form object includes means to handle all pending events, eg, to allow
canceling a lengthy operation.
317. Attempting to enter a .NET script under the debugger displays a descriptive
error message.
318. "Exception thrown at the target of invocation" error messages seen in .NET
scripts are expanded with error descriptions provided by the underlying
scripting objects.
319. Images linked from native Oracle data sources support selecting channels to
use for R, G, B and A data via the View - Display Options dialog.
Build 418
-------------------------------
320. (Fix) Exporting a component to an E00 file no longer fails if the
coordinate system of the component is not supported by E00 format.
321. (Fix) Previewing area border formatting of a drawing or theme in a map
window no longer crashes.
322. Exporting a table to a data source that supports NULL values makes
intrinsic, rank and script columns nullable.
323. Linking a drawing using coordinate columns automatically parses text values
in degree-minute-second format.
324. The component Properties dialog includes a new "..." button near the
component status readout, which invokes a dialog showing the data source of a
linked component. In addition to the data source, the dialog also shows the link
technology and the name of the rowset if the component is linked from a table or
query.
325. The Link / Share Status dialog invoked from the Properties dialog displays
the Enterprise server for a shared component and whether or not the component
caches data in the MAP file.
326. The Link / Share Status dialog invoked from the Properties dialog displays
the type of the link for a linked component (whether or not changes to the
component propagate to the data source) and the status of a shared component.
327. The Database Console includes a Global Filter button in the toolbar that
filters displayed database objects using regular expressions for names. Changes
to the global filter are saved between different sessions of Manifold. By
default, the global filter includes several masks suppressing the display of
system tables commonly found in Oracle databases.
328. Exporting an image to an Oracle database is no longer limited to about 32
MB of uncompressed image data.
329. The export dialogs used when exporting a drawing or image to an Oracle
database display the degree of similarity between the coordinate system of the
context Manifold component and the matched coordinate system registered in the
target database.
330. The export dialog used when exporting a drawing to an Oracle database
includes a new "Do not project data" option, which avoids projecting data from
the coordinate system of the component to the matched Oracle coordinate system
if they are different. By default, the option is turned off.
331. The export dialog used when exporting an image to an Oracle database
includes a new "Do not project data" option, which avoids projecting data from
the coordinate system of the component to the matched Oracle coordinate system
if they are different. By default, the option is turned off.
332. The export dialog used when exporting an image to an Oracle database
includes a new "Split data into tiles" option, which allows splitting image data
into tiles of specified size instead of sending image data in one chunk.
333. The export dialog used when exporting an image to an Oracle database
includes a new "Preserve image library tile structure" option which works for
image libraries that arrange individual image tiles using filenames. If the
option is turned on, the export creates a separate database tile for each file
in an image library, scaling pixels as necessary. If the option is turned off,
the export treats the image library as an ordinary image component and cuts
pixels into new tiles.
334. (Fix) Reporting a byte size no longer sometimes fails to round numbers,
resulting in "3.100 GBytes"-type reports.
335. (Fix) Linking an ECW or JPEG 2000 image no longer ignores coordinate system
data stored in an accompanying XML file.
336. The File - Export - Drawing dialog supports exporting a drawing to a KML
file (a file format used by Google Earth). The export dialog allows selecting
columns to use for object name and description (both optional).
337. The object model supports exporting data to KML.
338. (Fix) Decomposing a complex area to convex parts no longer sometimes
ignores or removes parts of the area.
339. Exporting complex areas to a SHP file works significantly faster.
340. (Fix) Attempting to obtain a saved selection of a table bound to a drawing
using a script no longer fails.
341. PixelSet objects representing selections in image and surface components
use significantly less memory and work significantly faster.
342. The object model includes means to obtain the dimensions and the visible
area covered by a component window.
343. The Application object includes means to display a message box with custom
icons and buttons.
344. (Fix) Attempting to use the LastAdded property on the RecordSet objects
representing all records in a particular table or query no longer fails.
345. The object model includes means to project a point onto a geom.
346. The object model includes means to triangulate a single area.
347. (Fix) The DecomposeConvex method of the Geom object has been renamed to
DecomposeToConvexParts, and has been adjusted to reject line geoms. Calling the
method using the old name is supported for compatibility reasons.
348. The query engine supports LONGITUDE and LATITUDE types.
349. (Fix) Altering data in a drawing linked from an Oracle table with no
associated coordinate system (NULL or zero SRID) no longer assumes the table
uses lat/lon, and projects data to and from lat/lon as necessary.
350. (Fix) Transferring data between objects in a linked drawing, for example,
during a transform, no longer fails.
351. Exporting a drawing or image to an Oracle database displays the error
returned by the database if the export fails.
352. (Fix) X (I), Y (I), Geom (I) and several other intrinsic columns in
drawings linked from data sources that can not be altered are no longer
writeable.
353. The export dialog used when exporting a drawing to an Oracle database
allows customizing the names of the identity and geometry columns. The default
name of the identity column is "ID". The default name of the geometry column is
"Geometry".
354. The export dialog used when exporting a drawing to an Oracle database
allows suppressing the creation of a sequence and trigger used to populate the
identity column.
355. The speed of sorting a large table using more than one column has been
significantly improved.
356. The number of records that can be handled by the query engine has been
significantly increased.
357. (Fix) Importing an ESRI ASCII grid file no longer sometimes imports garbage
height values for some pixels.
358. (Fix) Importing a DGN file no longer sometimes offsets all data in an X or
Y direction.
359. Importing a DGN file imports splines as curved shapes.
360. (Fix) Importing a DGN, DWG or DXF file no longer fails to close spline
shapes that have open ends that coincide with each other.
361. Importing a DGN, DWG or DXF file with external references dumps the names
of referenced files into the History pane.
362. (Fix) Image tiles downloaded from a remote server, for example, via the OGC
WMS interface, are no longer sometimes ignored by the system until the project
is saved or closed and re-opened.
363. Image libraries render data using more than one thread to increase the
performance on multi-processor (eg, dual-core) machines.
364. Running a .NET script first searches for referenced assemblies that use
relative paths in the Manifold installation folder and then searches in the
Config folder set in Tools - Options, File Locations.
365. (Fix) Exporting a layout to a PDF with transparency no longer fails if the
layout uses #000001 color.
366. (Fix) Deleting a legend item from the list of items in the Legend dialog no
longer sometimes removes the scrollbar even though some legend items are not
visible in the list.
Also fixed in this build are several bugs introduced during the beta campaign
(listed here for reference, but not included into the main list of items
representing changes since 6.50):
1. (Fix) Linking a drawing using coordinate columns no longer fails if the
columns are not numeric.
2. (Fix) Attempting to build contours or watersheds no longer fails.
3. (Fix) The Apply button in the Transform toolbar no longer gets disabled if
the active drawing layer does not contain any objects.
4. (Fix) Attempting to change the type of a column in a linked drawing no longer
sometimes crashes.
5. (Fix) Attempting to access MAP file data using the Manifold ODBC driver no
longer sometimes fails.
6. (Fix) Linking a satellite image from Google Maps no longer produces a
horizontal line.
Build 419
-------------------------------
367. A .NET script invoked in the context of a web site can access the Document
property of the Context object.
368. A .NET script can access the running script component using the Script
property of the Context object. If the script is an add-in script, both the
Script and the Document properties of the Context object return null values.
369. A non-.NET script can access the global Script object, which represents the
running script, and the global Document object, which represents the document
containing the running script. If the script is an add-in script, both the
Script and the Document objects are empty.
370. Importing or linking a drawing from a table or query using a geometry
column allows specifying a version column used to facilitate concurrent
multi-user editing. The version column has to be numeric (and writable).
371. Exporting a drawing to an Oracle database automatically creates a version
column used to facilitate concurrent multi-user editing. The name of the version
column can be customized.
372. The default name of the identity column used when exporting a drawing to an
Oracle database has been changed from "ID" to "OID" to avoid collisions with the
ID column that stores Manifold object IDs.
373. The Link / Share Status dialog invoked from the component properties dialog
allows selecting the editing mode of a linked drawing. The "overwrite changes
made by others" mode does not attempt to detect changes to the drawing objects
made by other people and overwrites such objects with local data. The "review
changes made by others" mode detects changes to the drawing objects made by
other people and resolves editing conflicts using the Review pane. The "review
changes made by others" mode is only enabled if the drawing has a version column
and is the default editing mode for such drawings. The editing mode only applies
to geometry data. Changes to non-geometry columns always overwrite data in the
data source.
Editing conflicts are detected by storing the version of each drawing object and
comparing that version to the version stored on the data source each time the
object gets changed. Whenever the local version of the changed object does not
coincide with its remote version, the system records an editing conflict.
Example: There are two users, A and B, who use the same linked drawing. The
linked drawing contains objects 1 and 2, with the version of each object
initially set to 10. A launches Manifold and opens a MAP file with the linked
drawing, which refreshes its data. B does the same. A changes object 1, which
increments its version to 11. B changes object 2, which increments its version
to 11. B attempts to change object 1. This creates an editing conflict, since
the local version of object 1 on B's machine is 10 but the remote version of
object 1 is 11 because object 1 has been changed (by A). B changes object 2
again, which increments its version to 12. There is no editing conflict, since
the local version of object 2 on B's machine is 11 and the remote version of
object 2 is also 11.
374. The new Review pane used for resolving editing conflicts in linked drawings
lists the IDs and types of objects involved in conflicts and the total number of
conflicts. Selecting an editing conflict and pressing the Use Local toolbar
button commits local changes made to the context object and uploads them to the
data source. Selecting an editing conflict and pressing the Use Remote toolbar
button discards local changes made to the context object and downloads the
latest version of this object from the data source. The Use All Local and Use
All Remote toolbar buttons commit or discard local changes made to all listed
objects.
There can be situations where the object participating in the editing conflict
is being changed while the person reviewing changes to the object decides how to
resolve the conflict. In this case, committing local changes to the object will
fail to resolve the conflict and will fetch the updated metric of the object
from the data source.
Example: There are two users, A and B, who use the same linked drawing. The
linked drawing contains objects 1 and 2, with the version of each object
initially set to 10. A launches Manifold and opens a MAP file with the linked
drawing, which refreshes its data. B does the same. A changes objects 1 and 2,
which increments their versions to 11. B attempts to change objects 1 and 2.
This created two editing conflicts. B chooses to use his local version of object
1 in spite of the changes made by A (see the next items for how he can choose
between the local and remote versions of the object). B selects object 1 and
presses the Use Local toolbar button. This sends B's version of object 1 to the
data source, and increments its version to 12. In the meantime, A changes object
2 one more time, which increments its version to 12 as well. B is unaware of
that change and reviews the outdated version of object 2. He chooses to use his
local version of object 2. He selects object 2 and presses the Use Local toolbar
button. This detects that the last version of object 2 seen by B (11) is not the
latest version of that object in the data source (12), downloads the latest
version of the object to B's machine and keeps the editing conflict open.
375. Editing conflicts in linked drawings are saved in the MAP file. This allows
postponing the review of a large number of editing conflicts until the user
decides to do so.
376. Loading a MAP file with a linked drawing which contains editing conflicts
makes editing conflicts inactive until the drawing is connected to the data
source. Normally, a linked drawing will automatically connect to its data source
when the user opens the MAP file, however, this behavior can be turned off with
the "Refresh linked components after opening file" option, or the data source
might not be available. Connecting a drawing to the data source by using the
Refresh Data or Relink command rematches conflict data and makes editing
conflicts active. Until the editing conflicts are active, they do not appear in
the Review pane as individual entities. The Review pane still reports the total
number of inactive editing conflicts and allows discarding all local changes by
using the Use All Remote toolbar button.
377. Refreshing data in a linked drawing validates the signature of the data
source and throws away all editing conflicts in case the signature has changed,
logging a message in the History pane. The signature of a data source contains
the description of its key columns.
378. The Review pane can preview a selected editing conflict. The local version
of the object metric is shown in semi-transparent red and the remote version in
semi-transparent blue.
379. The Review pane can go to or zoom to a selected editing conflict.
380. Switching the editing mode of a linked drawing from "review changes made by
others" to "overwrite changes made by others" discards all local changes, with
confirmation.
381. (Fix) Editing objects in a drawing linked from an Oracle database no longer
sometimes fails to submit changes to the database until the MAP file is closed
or saved.
382. Importing a surface from a Surfer GRD file derives the local offset and
local scale parameters of the surface coordinate system from the file header.
383. Keyboard shortcuts for panes have been changed to: Review = Alt-Shift-R,
Variables = Alt-Shift-A, Watches = Alt-Shift-W, World = Alt-Shift-O.
384. The Tools - Options, Colors pane includes the "Review Local" and "Review
Remote" entries which control colors of local and remote versions of a reviewed
object.
385. The NorthArrowStyle constants have been extended to cover all supported
north arrow styles.
386. (Fix) Dissolving drawing objects no longer fails if some of the resulting
objects are too small and get deleted due to the value of the location precision
parameter.
387. Drawing tables include the new Version (I) intrinsic column. Changing the
metric of a drawing object increments the value of the Version (I) column. For a
linked drawing which uses a version column, the values of the Version (I) column
will be the same as the values in the version column.
388. Linking a drawing using Database Console pops up the Import / Link Options
dialog which allows selecting a column to use as the version column.
389. Importing or linking a drawing from a native Oracle data source using
Database Console allows selecting an area of interest using the Import / Link
Options dialog. The "Require objects to be completely within area" option
switches between objects with at least one coordinate within the area of
interest (unchecked, the default) and objects with all coordinates within the
area of interest (checked). The read-only XY text boxes preceding and following
the editable text boxes contain the minimum and maximum XY coordinates of the
data set as reported by the data source.
390. The Import / Link Options dialog used when importing or linking a drawing
in Database Console allows specifying a name for the drawing.
391. The Confirmations page in the Tools - Options dialog includes a new
"Confirm bulk operations on editing conflicts" option which turns confirmations
for the Use All Local and Use All Remote toolbar buttons in the Review pane on
and off.
391. The Drawing object includes means to work with editing conflicts.
392. The Object object includes means to work with editing conflicts.
393. (Fix) Applying a layout template or saving a layout as a template no longer
ignores page filters for legend, north arrow, scale bar and text elements.
394. Linking images from OGC WMS servers and Manifold image servers supports
supplying login and password data in the form of http://user:password@host.
395. Exporting a drawing to a native Oracle data source creates a trigger that
automatically increments the version column whenever the object geometry column
gets changed, provided the "Create sequence and trigger" option is turned on.
396. The Import / Link Options dialog used when importing or linking a drawing
in Database Console includes a new "Rely on server to increment version
automatically" option which tells Manifold whether the data source will update
the version column after making changes to the geometry column automatically or
whether Manifold will have to do this. Attempting to import or link a drawing
from an Oracle data source detects the presence of a trigger running before or
after a value in the geometry column gets changed, and turns the "Rely on server
to increment version automatically" option on if such a trigger is found.
397. The parameters of stock CoordinateSystem objects exposed by the
CoordinateSystems property of the Application object have been adjusted so the
coordinate systems can be used as they are, without modifications to their
parameters.
398. The performance of the Normalize Topology and other transforms on complex
drawings has been significantly improved due to the reordering of read and write
operations. The transforms have been made more responsible to the Pause and
Cancel buttons.
399. The Database Console and Server Console dialogs have been made resizable.
400. Editing a cell in a table window supports navigating to the next and
previous editable cells using Tab and Shift-Tab key combinations respectively.
This applies to dialogs (eg, File - Create - Table) and panes (eg, View - Panes
- Control Points) as well.
Fixes of bugs introduced during the beta campaign:
1. (Fix) Importing or linking a drawing using coordinate columns no longer
assumes that the coordinate values are lat/lon even when the "Longitude /
latitude coordinates" option is turned off.
2. (Fix) Refreshing data in a linked drawing no longer marks it as modified.
3. (Fix) Adding or removing objects to or from a linked drawing no longer
sometimes crashes when the drawing's table is opened.
4. (Fix) Refreshing a drawing linked from another component in the same MAP file
refreshes that component.
Build 420
-------------------------------
401. The object model includes means to transform lat/lon coordinates to and
from USNG.
402. (Fix) Creating a buffer for a line with the buffer size less than 4 times
the location precision parameter no longer produces garbage.
403. (Fix) Exporting geometry data to SQL Server 2005 using ADO .NET no longer
fails.
404. (Fix) Refreshing data in a linked drawing no longer zooms the context
window to fit even if the coordinate system of the drawing did not change in a
significant way.
405. (Fix) Connecting to DB2 Express using ODBC or OLE DB no longer fails.
406. Connecting to a data source with no rowsets using Database Console leaves
the query text pane enabled to allow entering queries.
407. (Fix) Using Geom.Length and other properties of primitive geometry objects
that make use of coordinate system data no longer sometimes leaks memory.
408. Component objects include the Box property, used to retrieve the bounding
box of a component.
409. Database administrators can manage data stored on remote servers using the
new Administrator Console tool, available in the Tools menu. Similar to Database
Console, Administrator Console allows connecting to a data source, displaying
its contents and executing queries. In addition to that Administrator Console
allows supplying each database object with a friendly name, for further use
within Database Console. To enter a friendly name for a database object, select
the object and double click the Component cell or press F2.
Friendly names are stored in a metadata table and are available to all Manifold
clients connecting to the data source.
The metadata table is named MFD_META and contains three fixed-length or
variable-length text columns named OBJ, PROP and VAL. The OBJ column stores
names of database objects, the PROP column stores property names, and the VAL
object stores property values. If there is both a system table named MFD_META
and a user table named the same (as might be the case with Oracle data sources),
the system table is given preference.
To use friendly names within Database Console, connect to the data source with
the metadata table, and turn on "component view" using the Component View
toolbar button. If the data source does not contain a metadata table, the
component view button will be disabled. While in the component view, the dialog
will only show components that have been assigned friendly names. The Filter box
will work with friendly names as well.
410. The Administrator Console dialog has been made resizable.
411. Database Console displays database objects which have been assigned the
same component name using both the component name and the object name.
412. Connecting to a data source in Database Console automatically turns off
component view if the data source contains at least one component which has been
assigned a friendly name.
413. Administrator Console displays the number of objects in drawings and the
dimensions and the number of channels in images.
414. Administrator Console displays the projections of drawings and images.
415. SYS.xxx and MDSYS.xxx rowsets in native Oracle data sources are treated as
system rowsets. The global filter used in Database Console and Administrator
Console has been altered to exclude the "MDSYS\..+" mask and to include ".+\\.MFD_META"
and "MFD_META" masks to hide the metadata table used by Manifold tools by
default.
416. (Fix) The memory footprint of the Clip Intersect, Clip Subtract, Split and
Union transforms has been significantly reduced.
417. (Fix) The memory footprint of the Normalize Topology transform has been
significantly reduced.
418. (Fix) The memory footprint of Topology Overlay operations has been
significantly reduced.
419. The View - Projection, Edit - Projection and Edit - Projection, Current
Projection commands have been reworked into the new Edit - Assign Projection and
Edit - Change Projection commands. Assign Projection alters the current
projection of the component without altering its data. Change Projection
reprojects component data to the desired projection.
420. Attempting to reproject a component using the Change Projection command
before verifying the component's projection at least once using the Assign
Projection command fails with an error message.
421. Attempting to alter the current projection of a component using the Assign
Projection command after reprojecting it to another projection using the Change
Projection command (and, given the inability to use Change Projection before
having successfully used Assign Projection at least once, having confirmed its
former projection to be OK) displays a warning message, but allows continued
operation (eg, to change a projection in a minor way). The warning message can
be turned off by unchecking the "Confirm re-assigning projection after
projecting data" option in Tools - Options, Confirmations.
422. (Fix) The projection of profile components can no longer be altered. All
profile components bound to a particular surface are in the same projection as
the surface.
423. Opening a component whose projection has not yet been verified using the
Assign Projection command renders an info bar similar to that used by Internet
Explorer windows, with a text message prompting to verify the projection of the
component. Clicking the text message starts the Assign Projection dialog.
Clicking the X sign at the right side of the info bar hides the info bar so it
no longer appears in the window. Closing the window and opening the same
component in another window will restore the info bar. To turn off the info bar,
uncheck the "Prompt to verify projections of new components" option in Tools -
Options, User Interface.
424. Component objects expose a CoordinateSystemVerified property which allows
checking whether or not the coordinate system of a particular component has been
verified using the Assign Projection command, and altering the verification
state.
425. GPS Console includes means to set the datum used by the GPS receiver unit.
426. The Table Design dialog, Table Relations dialog and datum selection dialog
used by GPS Console have been made resizable.
In addition to the above changes, this build also includes two new Manifold
Image Server modules developed by the Manifold community, which allow linking
images from Yahoo! Maps and Microsoft Virtual Earth. After the release of 7.00
the source code for both these modules, similar to the source code for the
Google Maps module, will be put in the public domain, and will be available for
free download to anyone from SourceForge or a similar web site. While
manifold.net can not add features or fix bugs in these 3rd party products, we do
accept feedback related to their functionality and will make sure it gets to the
right people in the open source community.
Build 421
-------------------------------
427. The accuracy of basic geometric computations used in Clip Intersect, Clip
Subtract, Normalize Topology, Union and other transforms as well as query
functions has been significantly improved.
428. (Fix) Legend entries with multiline text no longer ignore the value of the
text alignment option set in the legend dialog.
429. Options related to the info bar have been moved to the Info Bar option
page. The new "Suppress prompt for non-default projections" option allows
showing the info bar only for components in the default Orthographic projection.
By default, the option is turned on.
430. Using a component with a coordinate system that has not yet been verified
pops up the info bar if the projection of the component is lat/lon and the
component has data outside the -180 ... 180 / -90 ... 90 lat/lon rectangle,
unless the "Prompt to verify projections of new components" option in Tools -
Options, Info Bar is turned off.
431. (Fix) Loading formatting data from an XML file no longer allows using
interval-based formatting on binary and boolean columns.
432. Saving formatting data to an XML string or file saves column binding info.
433. Loading formatting data from an XML string or file which contains a column
name using a script binds formatting to the desired column, if it exist and
supports the desired type of formatting.
434. (Fix) Running more than one web site with different values of
geocodingDatabaseFolder / geocodingExtensionFolder config file options no longer
sticks to using the pair of values belonging to the web site that was hit first.
435. The geocoding engine can geocode addresses using generic geocoding data
sources. A generic geocoding data source is a .NET object that supports the
Manifold Geocoding Server interface. The documentation of the Manifold Geocoding
Server interface and example implementations will be available after the final
release of 7.00. Individual geocoding data sources can be turned on and off in
Tools - Options, Geocoding.
436. There is a Manifold Geocoding Server module that uses the free geocoding
service on the Geocoder.us web site.
437. There are several new config file options controlling the behavior of the
geocoding engine when used from a web site:
country
The default country name.
geocodingServers
A list of Manifold Geocoding Servers to use, separated by commas.
preferMapPointToGeocodingDatabase
True or False. If True, gives MapPoint priority over the Manifold Geocoding
Database.
useGeocodingDatabase
True or False. Toggles the use of the Manifold Geocoding Database.
useGeocodingExtensions
True or False. Toggles the use of geocoding extensions.
useMapPointEurope
True or False. Toggles the use of MapPoint Europe.
useMapPointNorthAmerica
True or False. Toggles the use of MapPoint North America.
438. The File - Import - Drawing command includes means to import data from the
Manifold Geocoding Database. The user has to locate the STATES.DAT file in the
installed image of a Manifold Geocoding Database product (any version), supply
the list of county names to import, and the desired columns. Individual county
names are separated by a semicolon. A county name can optionally include a state
name, separated by a comma.
439. The object model includes means to import data from the Manifold Geocoding
Database using a script.
440. (Fix) Receiving data from a GPS unit via the GARMIN protocol no longer
drops data packets.
441. The File - Export - Web Page dialog includes an option to create an ASP
file for an OGC WFS interface. The WFS interface can be used with vector
components, such as drawings, themes and maps that contain drawing or theme
layers.
442. The Manifold WFS server supports HTTP POST.
443. The Manifold WFS server supports altering data within served component or
components.
444. The Application object includes means to translate binary data into a
string (used for handling POST requests) using the following method:
String BytesToString(Object bytes)
Converts an array of bytes into a string, automatically recognizing text
encoding.
445. The Application object includes means to create a coordinate system from an
EPSG code using the following method:
CoordinateSystem NewCoordinateSystemFromEpsg(String epsg)
Creates new coordinate system from given EPSG code.
446. There are new coordinate system presets for coordinate systems used in
Jordan. The value of the false northing parameter in the coordinate system
preset for Palestine Grid has been corrected.
447. KML export supports exporting images.
448. KML export creates KMZ files if the extension of the exported file is set
to ".kmz".
449. The Report combo under the "Current location" option in Tools - Options,
Status Bar includes an option to use USNG coordinates.
450. The columns shown in Administrator Console can be customized using the new
Columns toolbar button. Last used columns are saved between sessions. The data
displayed in the columns is fetched from the data source on demand.
451. The Statistics column in Administrator Console shows the number of records
in tables and views.
452. Administrator Console allows editing the coordinate system of a database
object by double-clicking the relevant cell in the Projection column.
453. Administrator Console allows enabling and disabling storing the formatting
of a database drawing object in the data source by double-clicking the relevant
cell in the new Format column. The formatting is stored in the metadata table in
XML format.
454. Refreshing data in a linked drawing which has been set to store formatting
data on the data source retrieves formatting data from the data source. Altering
the formatting sends updated formatting data back to the data source. Editing
conflicts are resolved via the Review pane. If the data source becomes
unavailable in the process of uploading updated formatting data, the changes are
saved in the component and appear as an editing conflict.
455. Selecting an editing conflict with formatting data in the Review pane
previews the server version of the formatting in drawing, map and theme windows
(the server version of the formatting is applied on top of whatever formatting
the theme has, to make it noticeable).
456. Administrator Console allows viewing and editing the location precision of
a drawing database object by using the Precision column.
457. Exporting a drawing to an Oracle data source allows specifying the value of
the location precision parameter.
458. Importing or linking a drawing using Database Console retrieves the value
of the location precision parameter from the data source, if it is available.
459. Importing or linking a drawing from another drawing in the same MAP file
using the Geom (I) intrinsic column inherits the coordinate system and the
location precision parameter of the source drawing.
460. Administrator Console allows editing the default link options (geometry
column and type, version column, the value of the "Rely on server to increment
version automatically" option, whether or not to store formatting on the data
source) and other properties (friendly name, coordinate system, precision) of a
database object by using the new Properties toolbar command.
461. Administrator Console allows editing the default link options of a database
table object with a binary column containing geometry data in one of the
supported geometry formats so it behaves like a drawing.
462. Administrator Console allows viewing triggers bound to a database objects
by using the Triggers toolbar button. At present, this only works on native
Oracle data sources.
463. Importing or linking a drawing using Database Console automatically skips
the Import / Link Options dialog if all options have been pre-set by a database
administrator using the Administrator Console.
464. Importing or linking data using Database Console defaults to component
names (that is, friendly names) if the component view is turned on.
465. The Projection dialog used with components linked from Oracle data sources
has been made resizable.
466. (Fix) Rendering a multiline text layout entry no longer puts too much space
between the text lines if the entry is rotated.
467. (Fix) Rendering a rotated layout entry no longer clips data that is still
inside the printable area of the layout page.
468. Displaying a rotated layout entry in a layout window displays the selection
box and the editing handles rotated.
In addition to the above changes, the build also fixes the following bugs
introduced during the beta campaign:
1. (Fix) Importing an image channel using Database Console assigns the created
image component the coordinate system of the image.
2. (Fix) Editing column data in a table or drawing linked from an OLE DB data
source no longer sometimes fails.
3. (Fix) Attempting to unlink a table or drawing linked from an OLE DB data
source no longer sometimes crashes.
Also of note, the name of the internal datum used for images linked from Google
Maps has been changed from "WGS84 Google" to "WGS84 Auto", since the datum
appears to be also used by Virtual Earth and Yahoo! Maps. The coordinates in
images linked from Google Maps using builds prior to this one may now be
slightly off. The coordinate system issues with images linked from Virtual Earth
and Yahoo! Maps have been resolved.
Build 422
-------------------------------
(an instrumented build for testing)
Build 423
-------------------------------
469. (Fix) Linking a table from an OLE DB data source no longer fails to
recognize primary key columns.
470. (Fix) The Type property of the Geom object no longer returns a number
instead of a GeomType constant.
471. The Geom object includes a CenterInner property that computes an inner
centroid of an area.
472. Geocoding dialogs allow standardizing and geocoding addresses without a
Country column.
473. GPS Console autodetect a switch in GPS protocol from GARMIN to NMEA.
474. Captions of dialogs used to export data to Oracle data sources have been
changed to Export Oracle Drawing (was: Oracle Data Source) and Export Oracle
Image (was: Oracle Image).
475. The Application object includes a SerialNumberHashHex property to retrieve
a hash of the serial number in hexadecimal notation, for use in activation
schemes implemented by third-party add-in vendors.
476. The new Tools - Batch Export tool allows exporting multiple drawings,
images and surfaces to a native Oracle data source.
477. The Batch Export dialog has been made resizable.
478. Exporting a set of components using the Batch Export dialog automatically
unchecks the components as they are exported to facilitate canceling the
(potentially lengthy) export operation before completion and restarting it from
where it stopped.
479. Exporting a table to an ADO.NET, ODBC, OLE DB or native Oracle data source
allows selecting columns to export.
480. Exporting a drawing to an MDB file exports the ID column as an
autoincremented column.
481. Exporting a drawing to a SQL Server data source makes the ID column the
IDENTITY column.
482. Database access code has been cleaned up to ensure compatibility with DB2
Express-C. OIn a drawing linked from a DB2 Express-C data source the following
limitations remain: adding a new object and immediately editing it without
refreshing the drawing creates an editing conflict, adding a new object and
immediately deleting it without refreshing the drawing fails. Therefore, always
refresh data after adding a new object when working with DB2 geometry storage.
483. The "Undelivered message call" error message popping up due to activation
problems has been replaced with "Authentication error".
484. Launching Manifold for the first time or attempting to activate Manifold or
a Manifold extension displays a warning message if the context user account will
not be able to complete the activation due lack of permissions.
485. Fetching an Activation key requires a serial number and a "system ID" used
to identify the system (displayed in both Activate and Activate Extension
dialogs).
486. Functions related to geocoding have been separated into the new Geocoding
Tools extension. Administrator Console and Batch Export tools have been
separated into the new Database Administrator edition. Functions related to
native Oracle data sources are restricted to Enterprise edition. The
Professional with Debugger edition has been merged into Professional edition.
There is a new Personal edition, which is equivalent to Professional edition
without the MapServer object and the File - Export - Web Page command.
The edition hierarchy is: Personal -> Professional (can host web sites) ->
Enterprise (can access Enterprise storages and native Oracle data sources, and
export E00 and supress IMS logo) -> Universal / Database Administrator.
Universal includes Business Tools, Surface Tools and Geocoding Tools, but not
Administrator Console and Batch Export. Database Administrator includes
Administrator Console and Batch Export, but not the extensions.
The runtime edition hierarchy is: Professional Runtime (can host web sites) ->
Universal Runtime (can supress IMS logo). Universal Runtime includes Business
Tools, Surface Tools and Geocoding Tools.
487. Activation dialogs include means to fetch Activation keys automatically via
the Activation web service. If the web service can not be reached, the dialogs
allow the user to edit proxy server configuration or to activate manually by
fetching an Activation key using some alternative Internet connection.
488. There is a new License Server product, used to manage operation of
multiple, floating instances of Manifold (all of the same edition) in large
enterprise environments without the need for serial numbers and Activation keys
on each machine. License server is not either an interactive or runtime GIS but
can only be used to manage operation of other Manifold instances.
Build 424
-------------------------------
489. (Fix) Clipping lines to an area using Clip with (Intersect) no longer
sometimes leaves portions of lines unclipped.
490. (Fix) Refreshing a linked table no longer sometimes fails to adjust names
of linked columns if there is an active or rank column with the same name.
491. (Fix) Selecting a viewbot in the ViewBots pane which has not been refreshed
and refreshing its value manually by pressing the Refresh or Refresh All toolbar
button no longer fails to enable the selection toolbar buttons.
492. (Fix) Working with a drawing whose table includes an active column computed
on the fly no longer sometimes hangs.
493. (Fix) Rendering a rotated layout element that is close to the side of the
layout page no longer sometimes renders nothing.
494. (Fix) Drawings and labels no longer allow inserting objects and labels with
metrics that contain invalid floating-point coordinates (NaNs). This protects
against errors in imports and scripts.
495. (Fix) Running a transform on a theme component no longer sometimes crashes.
495. Clusterize, Clusterize (Advanced), Clusterize (Visual), Color, Topology
Overlay and Transfer Heights dialogs, which save data into drawing columns,
allow working with linked drawings.
496. License server installations no longer allow working without an Activation
key.
497. The splash screen, the contents of the About box and all other
version-specific readouts have been adjusted to use 7.00 nomenclature.
498. Importing a drawing from Geocoding Database files allows turning automatic
formatting on and off via an option.
499. The response returned by the WFS server has been optimized to be as small
as possible.
500. Administrator Console and Database Console no longer allow a drawing to
have a version column if the drawing does not contain a primary key.
501. Importing a drawing from a VMap0 data set no longer hangs on certain types
of malformed coverages.
502. Using the Manifold object model from an external application automatically
sets the precision used for floating-point computations to an optimal level upon
entering Manifold and restores it to the level used by the application upon
leaving Manifold.
503. The performance of importing a drawing from a VMap0 data set has been
significantly improved.
We have also fixed the following issues introduced during the beta campaign:
1. (Fix) Administrator Console no longer fails to report the value of the Format
column for tables treated as drawings.
2. (Fix) Altering formatting of a linked drawing whose formatting is stored on
the data source no longer sometimes creates an editing conflict.
3. (Fix) Importing a drawing from another MAP file using File - Import -
Component no longer sometimes fails to import formatting of point objects.
4. (Fix) Attempting to compute a maximum column value using a viewbot no longer
produces a minimum column value.
5. (Fix) Computing the lat/lon bounds of an area shown in the active window when
attempting to link an image from a Manifold image server or from TerraServer no
longer returns shifted data if the component shown in the active window uses the
"Auto" datum, typically assigned to images linked from Google Maps, Yahoo! Maps
or Microsoft Virtual Earth.
Build 425
-------------------------------
504. (Fix) Disconnecting a working GPS unit connected via USB / GARMIN no longer
sometimes crashes.
505. (Fix) Working with a GPS unit connected via USB no longer sometimes loses
data packets.
506. Text columns in metadata tables used to store names, coordinate systems and
other data for Manifold components stored in external databases can be fixed
length.
507. (Fix) Deleting a column from a standalone table no longer sometimes selects
or unselects table records.
508. (Fix) Importing an ERDAS GIS file no longer sometimes creates a palette
bound to a surface instead of a standalone palette.
509. (Fix) Attempting to import a malformed LULC CTG file no longer sometimes
crashes during cleanup.
510. (Fix) Canceling the import of an ADF file no longer sometimes fails to
delete components created during the import and thus leaving the MAP file in an
inconsistent state.
511. (Fix) Importing a COQ file no longer sometimes fails.
512. (Fix) Importing an ERDAS IMG file no longer sometimes produces a black
rectangle.
513. (Fix) Importing an IMDISP image by pointing to an IMG file instead of a LBL
file no longer fails.
514. (Fix) Importing an S-57 file no longer sometimes jumps progress to 100% at
the very beginning.
515. (Fix) Editing a comments, query or script component no longer joins undo
actions for separate editing operations.
516. Pasting drawing objects with new columns into a linked drawing tries to
create new columns as NULL-able to have a better chance of succeeding.
517. (Fix) Attempting to convert a small palette image to a compressed image no
longer crashes.
518. (Fix) Pressing the Apply toolbar button in the Format dialog for drawings
or Display Options dialog for surfaces more than once no longer sometimes
crashes.
519. (Fix) Placing the cursor into the top pixel row or into the right pixel
column of an image or surface no longer fails to report the XY coordinates of
the cursor in the status bar.
520. The KML file filter has been changed to cite KMZ files as well.
521. The IsRing query function has been adjusted to return False for lines with
more than one branch.
522. OLE DB code has been adjusted to allow uploading binary data to MySQL data
sources.
523. The OPTIONS query clause supports the new Precision(...) construct that
allows setting the desired location precision for clients linking the query as a
drawing.
524. Establishing a database connection for a component linked from an ODBC data
source automatically descends to read-only mode if connecting in read-write mode
returns a cursor that can not be used to operate the component.
525. Importing an S-57 file performs significantly faster.
526. Attempting to convert an image to a compressed format via Image - Convert
To displays any error messages returned by the ECW / JPEG2000 compression code
if the conversion fails.
527. The Assign Projection and Change Projection commands in the Project pane
context menus for labels bound to drawings and profiles have been disabled.
528. (Fix) Importing a DGN, DWG or DXF file no longer sometimes fails when
handling certain edge cases of extrusion vectors.
529. (Fix) Pasting layout elements from a layout bound to a component into a
layout not bound to a component between different sessions of Manifold no longer
sometimes crashes.
530. (Fix) Spatial joins in queries no longer sometimes over-optimize distance
tests.
531. (Fix) The Table - Match - Drawing dialog no longer fails to list latitude /
longitude columns in the X / Y combos.
532. (Fix) Importing a GRASS file no longer sometimes creates a surface with
height values too large or too small.
533. (Fix) Failing to import a malformed HDF SeaWiFS file no longer leaves the
file opened until Manifold is shut down.
534. (Fix) Importing a surface from a 1-bit raw binary file no longer fails.
535. Importing a TIGER/Line data set with malformed timestamp data autocorrects
timestamps.
536. The coordinate systems for Belgium, Finland, Liechtenstein and Switzerland
used by Oracle Spatial have been mapped to their Manifold equivalents.
537. Downloading data from a GPS unit using GPS Console allows reusing already
downloaded data.
538. Importing a drawing from a malformed DWG file recovers from certain types
of coordinate errors.
539. (Fix) The Delete Ending With and Leave Ending With table transforms no
longer work inconsistently when run on a pair of columns.
540. (Fix) Removing a target drawing when downloading data from a GPS unit using
GPS Console no longer sometimes crashes.
We have also fixed the following issues introduced during the beta campaign:
1. (Fix) Formatting an Enterprise storage no longer deletes the metadata table.
2. (Fix) Counting the number of selected pixels in a newly created image or
surface using SELECT Count(*) FROM [Image] WHERE [Selection (I)]; no longer
returns a non-zero value.
3. (Fix) Importing a malformed ADF TIN file no longer sometimes crashes.
4. (Fix) Importing a TIF with an RGBA image no longer sometimes fails.
5. (Fix) Importing a SPOT file with a filename longer than 4 characters no
longer fails.
6. (Fix) Importing an ERDAS IMG file no longer uses wrong names for created
image or surface components.
7. (Fix) Layout windows no longer fail to render editing handles for rotated
layout entries, if the "Print using GDI+" option is turned off.
8. (Fix) Editing a comments, query or script component no longer sometimes fails
to delete text (and no longer sometimes deletes too much text).
9. (Fix) Running a .NET add-in no longer fails due to a missing Document object.
10. (Fix) It is no longer possible to add or remove objects in a checked out
drawing if the drawing's table is not checked out.
11. (Fix) Checking in a table bound to a drawing automatically checks in the
drawing, if the drawing is checked out, and vice versa.
12. (Fix) The status bar no longer fails to report cursor location using USNG
coordinates if the coordinate system of the context component is different from
standard lat/lon.
13. (Fix) Loading a read-only MAP file with a linked drawing created by 6.50 or
an earlier version of Manifold no longer fails to relink or unlink the drawing.
14. (Fix) Selecting a folder in the projection tree in the Assign Projection or
Change Projection dialog and clicking OK no longer sometimes crashes.
15. (Fix) Refreshing data in a drawing linked from a query from the drawing's
table window no longer sometimes crashes.
16. (Fix) Importing an AVHRR data set no longer sometimes crashes when
generating a comments component.
17. (Fix) Modifying a RecordSet object bound to a standalone table no longer
sometimes crashes.
18. (Fix) Attempting to delete an object in a drawing linked from a SQL Server
table no longer sometimes fails to work in case the object has been modified
shortly before the deletion.
19. (Fix) Clipping the coordinates of a drawing when projecting to an
Orthographic, Gnomonic or similar projection no longer sometimes miscomputes the
clipping area which results in no clipping being done.
20. (Fix) Linking a Manifold IMS web site as an image via the Manifold Image
Server interface no longer sometimes displays wrong data due to coordinate
system issues.
New Help Topics in 7.00 SP1
---------------------------------------
A Flashy Demo - Web Queries and KML
CREATE DRAWING Statement
Data Storage Strategies
Database Administrator Edition
Database Object Projection
Database Object Properties
Database Object Triggers
DROP DRAWING Statement
Example: Storing a Drawing in Oracle
Example: Storing an Image in Oracle
Export Drawing - KML, KMZ
Export Drawing - Oracle
Export Image - ECW / JPEG2000
Export Image - KML, KMZ
Export Image - Oracle
ExportKml (object)
Extensions
File - Link
Fun with Google Earth
Gall
Geocoding Data Sources
Geocoding Server Interface
Geocoding Tools
Guyou
Help - Manifold on the Web
Help - Contents
Help - Index
Help - Search
IBM DB2 Express-C Edition
Image - Create Index Drawing
Image Libraries
Image Server Interface
Import a Drawing from the Geocoding Database
Import Drawing - ADF
Import Drawing - Geocoding Database
Import Image - JPG, JPEG
Import Surface - ADF
ImportGcdb (object)
Installing and Activating a Manifold Extension
Installing Oracle
Intermediate Levels and Pyramids
Labels - Synchronized
Labels - Unlink
Linked Drawings from Geocoded Tables
Linked Images from Google Servers
Linked Images from Manifold Image Servers
Linked Images from Manifold IMS Web Sites
Linked Images from Microsoft Virtual Earth
Linked Images from Oracle Servers
Linked Images from Yahoo! Maps
LinkEditMode (constant)
Manifold Geocoding Servers
Manifold System License Server
MessageBoxResult (constant)
MessageBoxType (constant)
Multi-User Editing of Linked Drawings
Oracle Express Edition
Oracle Spatial Facilities
Peirce
PointUSNGPrecision (constant)
Project Pane - Open Data Source
Storing Drawings in SQL Server
Tools - Administrator Console
Tools - Batch Export
Terrain - Snap to Surface
Using Administrator Console
Van der Grinten IV
View - Panes - Review
View - Properties - Link / Share Status
What about Ajax?
What's New
What's New in 7.00
Help Topics Renamed in 7.00
---------------------------------------
SQL Server Desktop Engine renamed to SQL Server Express Edition
Help Topics Deleted in 7.00
---------------------------------------
Dynamic Drawings
Edit - Projection
Edit - Projection - Current Projection
Linked Drawings and Geocoded Tables
View - Projection
Kudos
---------------------------------------
As usual with a major new Manifold release, thousands of suggestions and other
reports were received from Manifold users worldwide for features and bug fixes
incorporated into 7.00.
The manifold.net team would like to thank all 7.00 beta testers who so
generously contributed their time and advice. Many countries were represented,
including the US, Canada, Mexico, UK, Spain, the Netherlands, France,
Switzerland, Italy, Germany, Austria, Russia, India, Japan, Malaysia, Singapore,
Australia, New Zealand and South Africa.
Although many beta testers worked very hard, even in this elite group some
contributors stood out. Special thanks go out for an extra effort to David
Brubacher (Canada), James Burn (Canada), Tobie de Villiers (South Africa), Klaus
Engelberg (Germany), Antonio C. González Toro (US), Simon Greener (Australia),
Graeme Greenwood (Australia), Robert Heitzman (US), Henry Holland (UK), William
Howell (US), Arthur Lembo (US), Abram Pointet (Switzerland), Peter Ronning
(Canada) and Mike Sumner (Australia). Colin Driscoll (Australia) especially went
beyond the call of duty to patiently download and test in the field special
builds to eliminate a bug in GPS connection via USB.
The outstanding support for Oracle within 7.00 would not have been possible
without the encouragement and first class professionalism of the Oracle Spatial
development team. Special thanks go out to Dan and Justin for your support and
for running the interface between the companies and to Xavier for making all
this possible.
Manifold would also like to welcome the IBM DB2 team in Toronto, San Jose, Menlo
Park and New York to the product effort, with special thanks to Alvin, Boris,
Melody and Les for your support and to IBM for granting permission to
redistribute DB2 Express-C on the Manifold DVD.
Thanks everyone for helping make 7.00 a terrific release!
|
Home Page -
Products -
Search -
Support -
Shopping -
News -
Online Store Prices, terms and conditions, and product specifications subject to change without notice. Please contact Manifold Net with any special needs or requests. |