MapInfoProReleaseNotes PDF
MapInfoProReleaseNotes PDF
MapInfoProReleaseNotes PDF
Version 12.5.5
Release Notes
This document provides information about the resolved issues
and the known issues that are important to MapInfo Pro users.
MapInfo Pro 12.5.5 is a cumulative update that includes all
updates supplied with the 12.5.4 and 12.5.3 Maintenance
Releases.
Contents:
Before You Continue
Upgrading MapInfo Pro
Advanced Installation for System Administrators
Maintenance Release 12.5.5
Maintenance Release 12.5.4
Maintenance Release 12.5.3
2
2
2
4
4
6
Release Notes
Release Notes
Issue Number
MIPRO-65092
Known Issues
Installing 32-bit and 64-bit versions of MapInfo Pro on to the same Machine
You should not install the 32-bit and 64-bit versions of MapInfo Pro into the same directory.
If you install any 32-bit version of MapInfo Professional (including version 12.5.0) after installing
MapInfo Pro 12.5.4 on to the same machine, you will encounter an issue when installing both
products into the same directory. The 32-bit version of MapInfo Professional does not recognize
that MapInfo Pro 12.5.4 is already installed, so the 32-bit version of the MapInfo Professional
installation wizard lets you install into the same folder that 12.5.4 is already installed to. This results
in files being overwritten, so that neither product operates correctly.
Release Notes
If this issue occurs, uninstall both products. Reboot the computer, then reinstall both the 32-bit
and 64-bit versions to different directories.
Side by side installation of MapInfo Pro 12.5.1 and MapInfo Professional 12.5 PDF Printer
Installing MapInfo Professional 12.5 32-bit after installing MapInfo Pro 12.5.4 will result in the
MapInfo PDF printer being downgraded from Version 4.5.3.9 to version 4.5.3.5. This will cause
MapInfo Pro 12.5.1 to close unexpectedly when attempting to print a GeoRegistered PDF or a
Layered PDF with attributes.
In this case, you will need to do a complete uninstall and re-install of MapInfo Pro 12.5.4.
Issues with keyboard focus
There are some situations where the keyboard focus is not being set to the active window when
moving from docked to tabbed to floating.
Calculate Statistics
The Calculate Statistics command is missing in this release.
Issue with dual monitors
You may lose floating windows when moving from two monitors to one. On the HOME tab, in the
Window group, click Recover Off Screen Windows to restore the windows.
Issue with shortcut key in Layer window
In the Layer window, the short cut key (F2) to rename a map may not work properly. If you select
a map and press F2, it highlights the entire text, but once you click inside the cell it turns uneditable.
Issues with Layout Designer
When you have a large number of maps open, the Map drop-down list in the LAYOUT tab may
not work correctly.
Ribbon items not displaying properly
Items added to the ribbon when a tool is loaded through the Tool Manager do not appear when a
map window is in a floating mode.
View/Edit Metadata option does not exist in this version
The View/Edit Metadata menu option is not available when you right click on a map in the Layer
Control window. This option is present in the earlier versions.
CTRL + F4 does not close Tool windows.
Pressing CTRL+F4 does not close Tool windows. It does, however, close other document windows.
MapBasic types which contain strings may not be passed correctly to WinAPI DLLs in 64-bit
Release Notes
If a DLL function takes a struct type input argument, you can declare a type in MapBasic equivalent
to the API struct a function is declared. For structs defined with a string pointer member, there are
problems calling into the x64 WinAPI DLLs if you define this equivalent struct member as a String
type. Instead, you need to define the struct member as an IntPtr type. For 32-bit MapInfo
Professional, the equivalent WinAPI DLL struct could be defined with a String type.
Error message when accessing help from any dialog
Users experiencing an issue using the Help System after installing MapInfo Pro 12.5.3 should
delete the mapinfopro12_5_64bit cache folder under the AppData folder (for example,
C:\Users\%USERNAME%\AppData\Local\mapinfopro12_5_64bit).
Issue Number
MIPRO-59627
Changing zoom while using custom polygon tool does not work correctly.
If you change the zoom while using a custom poly tool, the rubber band polyline may not draw
properly.
Resolution: Fixed.
MIPRO-59337
MIPRO-61624
MapInfo Pro stops working when a layer is selected and display of Grouplayer is disabled
through MapBasic.
Resolution: Fixed.
Release Notes
Note: The MAPINFOPRO.MNU file is not updated by this maintenance release. However, we have
updated the commands' resources in the MAPINFOPRO.MNU file which you can download
from www.mapinfo.com/resources. You must restart MapInfo Pro for the changes to take
effect.
SpiderGraph
The SpiderGraph tool creates lines between objects in a single table, or between objects from two
different tables based on a common identifier. For example, if you have Stores and Customers as
two tables, and both tables have a store identifier column then the SpiderGraph tool can create a
new table with lines connecting customers to their store.
The resulting table contains the lines as well as chosen attributes from the input table(s), along with
a column that stores the length of each line. The lines can be color-coded based on their attribute
of origin.
To obtain more MapInfo Pro resources and downloads, visit www.mapinfo.com/resources.
Note: If you have already started MapInfo Pro before installing the maintenance release, you will
have to add the new tools manually.
Release Notes
If you double-click a map name, the focus goes to the map window, so that the arrow keys pan
the map. This gesture is useful when you want to put the focus in the map window, but you do not
want to click in the map window because doing so might clear a table selection.
Within the Layers list, when you use the Up arrow key or the Down arrow key to change the
selected map name, that map does not automatically come to the front.
With a map name selected in the layer list, press Enter to bring that map to the front. Afterwards,
you can continue to use the arrow keys to move through the layer list.
With a map name selected in the layer list, press Ctrl+Enter to bring the map to the front, and put
the focus on the map (so that subsequent arrow keys pan the map). This gesture is useful when
you want to put the focus in the map window, but you do not want to click in the map window
because doing so might clear a table selection.
Minimized Windows now treated as Hidden
The main purpose of a minimized window in older versions of MapInfo Pro was to get them out of
the way and in effect make them invisible. In MapInfo Pro version 12.5.1, we introduced the concept
of hidden windows. However, we ran into several problems. The minimized windows started to
obstruct the status bar. In version 12.5.1, while reading a workspace created by older versions of
MapInfo Pro, we bring up the normal windows as tabbed windows. But minimized windows are
considered floating windows even though their non-minimized state would be tabbed.
Due to such issues and other inconsistencies, in version 12.5.3, we treat minimized windows as
hidden. You can use the Window List or Workspace Explorer options to access these hidden windows.
New Features in MapBasic
The following features have been added/updated in MapBasic:
Removing frames from Layout Designer windows
You can delete frames from Layout Designer windows using the MapBasic program. The Remove
Designer Frame statement, which originally worked only on Legend Designer windows, can now
be used on Layout Designer windows as well. If the Window clause specifies a Layout Designer
window ID, the statement removes frames from that Layout.
If you omit the Window clause, the statement operates on the frontmost open window, that is either
a Legend Designer or a Layout Designer window.
Altering Text frames in Layout Designer windows
MapBasic programs can now alter text frames from Layout Designer windows. The Alter Designer
Text statement, which originally worked only on Legend Designer windows, can now be used on
Layout Designer windows as well. The MB Syntax is has not changed. But it now supports text
frames in the Layout Designer.
The following statement can be used to alter the text string, font style, or text position.
Alter Designer Text
[ Window window_id ]
Release Notes
[
[
[
[
ID textframe_id [
Text frame_text ]
Font... ]
Position ( x, y ) [ Units paper_units ] ] ] ]
If you omit the Window clause, the statement operates on the frontmost open window, that is either
a Legend Designer or a Layout Designer window.
Altering frame position in Layout Designer windows
MapBasic programs can now alter frame positions from Layout Designer windows. The Alter Designer
Frame statement with the Position clause can now be used on Layout Designer windows as well.
The MB Syntax has not changed but it now supports moving frames in the Layout Designer using
the Position clause.
The Position clause in the following statement can be used to alter the layout designer frame position.
Alter Designer Frame
[ Window legend_window_id ]
Id { frame_id }
[ Position ( x, y ) [ Units paper_units ] ]
[ Title [ frame_title ] [ Font... ] ]
[ SubTitle [ frame_subtitle ] [ Font... ] ]
[ Columns number_of_columns ] |
[ Height frame_height [ Units paper_units ] ]
[ Region [ Height region_height [ Units paper_units ] ] ]
[ Region [ Width region_width [ Units paper_units ] ] ]
[ Line [ Width line_width [ Units paper_units ] ] ]
[ Auto Font Size { On | Off } ]
[ Order { Default | Ascending | Descending |
{ Custom id | id : id [ , id | id : id ... ] ... } } ]
[ Style [ Font... ]
[ ID { id } Text { style_name } ]
[Line Pen... | Region Pen... Brush... | Symbol Symbol... ] ]
[ , ... ]
The other clauses are not supported for layout frames.
If you omit the Window clause, the statement operates on the frontmost window, that is either a
Legend Designer or a Layout Designer window.
Refreshing Image frames in Layout Designer windows
MapBasic programs can refresh an image frame in a Layout Designer window if the underlying
image source file has changed. The new Refresh Designer Frame statement can now be used to
refresh image frames.
Refresh Designer Frame
[Window window_id] ID frame_id [, frameID ...]
where, "window_id" is a Layout Designer window's integer window
identifier. If no window is specified the command assumes the frontmost
Layout Designer window.
Release Notes
These are not included with the Maintenance Release, you can add the following entries in the
MAPINFOW.PRJ file manually.
The file is located under the Tools folder where MapInfo Pro is installed (for example, under
C:\Program Files\MapInfo\Professional).
"Longitude / Latitude (Japan Datum 2011 JGD2011)", 1, 162
"Longitude / Latitude (Timbalai 1948, Modified Everest Ellipsoid)", 1,
Release Notes
10
163
"Longitude / Latitude (MAGNA-SIRGAS)\p4686", 1, 165
"Longitude / Latitude (GDM2000 Datum)", 1, 164
"Japanese Zone I (Japan Datum 2011 JGD2011)", 8, 162, 7, 129.5, 33,
0.9999, 0, 0
"Japanese Zone II (Japan Datum 2011 JGD2011)", 8, 162, 7, 131, 33,
0.9999, 0, 0
"Japanese Zone III (Japan Datum 2011 JGD2011)", 8, 162, 7, 132.166666,
36, 0.9999, 0, 0
"Japanese Zone IV (Japan Datum 2011 JGD2011)", 8, 162, 7, 133.5, 33,
0.9999, 0, 0
"Japanese Zone V (Japan Datum 2011 JGD2011)", 8, 162, 7, 134.333333,
36, 0.9999, 0, 0
"Japanese Zone VI (Japan Datum 2011 JGD2011)", 8, 162, 7, 136, 36,
0.9999, 0, 0
"Japanese Zone VII (Japan Datum 2011 JGD2011)", 8, 162, 7, 137.166666,
36, 0.9999, 0, 0
"Japanese Zone VIII (Japan Datum 2011 JGD2011)", 8, 162, 7, 138.5, 36,
0.9999, 0, 0
"Japanese Zone IX (Japan Datum 2011 JGD2011)", 8, 162, 7, 139.833333,
36, 0.9999, 0, 0
"Japanese Zone X (Japan Datum 2011 JGD2011)", 8, 162, 7, 140.833333,
40, 0.9999, 0, 0
"Japanese Zone XI (Japan Datum 2011 JGD2011)", 8, 162, 7, 140.25, 44,
0.9999, 0, 0
"Japanese Zone XII (Japan Datum 2011 JGD2011)", 8, 162, 7, 142.25, 44,
0.9999, 0, 0
"Japanese Zone XIII (Japan Datum 2011 JGD2011)", 8, 162, 7, 144.25, 44,
0.9999, 0, 0
"Japanese Zone XIV (Japan Datum 2011 JGD2011)", 8, 162, 7, 142, 26,
0.9999, 0, 0
"Japanese Zone XV (Japan Datum 2011 JGD2011)", 8, 162, 7, 127.5, 26,
0.9999, 0, 0
"Japanese Zone XVI (Japan Datum 2011 JGD2011)", 8, 162, 7, 124, 26,
0.9999, 0, 0
"Japanese Zone XVII (Japan Datum 2011 JGD2011)", 8, 162, 7, 131, 26,
0.9999, 0, 0
"Japanese Zone XVIII (Japan Datum 2011 JGD2011)", 8, 162, 7, 136, 20,
0.9999, 0, 0
"Japanese Zone XIX (Japan Datum 2011 JGD2011)", 8, 162, 7, 154, 26,
0.9999, 0, 0
"--- Universal Transverse
"UTM Zone 51 (Japan Datum
500000, 0
"UTM Zone 52 (Japan Datum
500000, 0
"UTM Zone 53 (Japan Datum
500000, 0
"UTM Zone 54 (Japan Datum
500000, 0
"UTM Zone 55 (Japan Datum
Release Notes
11
500000, 0
"UTM Zone 56 (Japan Datum 2011 JGD2011)", 8, 162, 7, 153, 0, 0.9996,
500000, 0
"UTM Zone 57 (Japan Datum 2011 JGD2011)", 8, 162, 7, 159, 0, 0.9996,
500000, 0
New Projections
Parameters
Descriptions
Name
Projection Number
Datum
Units
7 Units in meters
Origin Longitude
Origin Latitude
Scale Factor
False Easting
False Northing
The new projection #35 will create a version 1252 TAB, MIF, and WOR file.
The other new datum numbers will create a version 1252 WOR and MIF file, however, they may
not require a TAB version change to 1252 as they use an already supported ellipsoid. The TAB
version change depends on other features used in the data, see the MapInfo Pro help topic for
File Versions and TAB, MIF/MID, and WOR Support.
Release Notes
12
These are not included with the Maintenance Release, you can add the following entries in the
MAPINFOW.PRJ file manually.
The file is located under the Tools folder where MapInfo Pro is installed (for example, under
C:\Program Files\MapInfo\Professional).
"Peninsular RSO GDM2000 Datum", 35, 164, 7, 102.25, 4, 323.025796466667,
323.130102361111, 0.99984, 804671, 0
"Peninsular RSO Kertau Datum", 35, 47, 7, 102.25, 4, 323.025796466667,
323.130102361111, 0.99984, 804671.2996, 0
"East Malaysia (BRSO) GDM2000 Datum", 35, 164, 7, 115, 4, 53.31582047,
53.13010236, 0.99984, 0, 0
"East Malaysia (BRSO) Timbalai Datum", 35, 163, 7, 115, 4, 53.31582047,
53.13010236, 0.99984, 0, 0
Issue Number
MIPRO-39353
>Exporting a map with translucent layer using bitmap fill patterns sometimes does not export
colors correctly.
Resolution: Fixed. The exported images, from Save Window As, now look as good as they
appear on the screen.
MIPRO-42466
MIPRO-50913
The default output format for the DescribeFeatureType request (which returns a schema with
the table structure) was changed between WFS 1.0 and WFS 1.1. We were correctly using
the new default if the server supports POST requests, but not if the server only supports GET
requests. If the server also only supports WFS 1.1 and not the older schema format, it produces
an error.
Resolution: Fixed.
Release Notes
13
Issue Number
MIPRO-45949
Oracle Spatial 12c : In the Open DBMS Table dialog box, do not show the index tables of type
MDXT%.
Resolution: Fixed.
Now any Oracle table name starting with MDXT_ are filtered out in the Open DBMS Table
dialog box. Users should not name their Oracle tables starting with MDXT_.
MIPRO-41165
MIPRO-37789
If the cutter/target object has some polygons with 3 points, the exterior polygons were not
getting correctly classified and some object processing operations like overlap calculations
and erase were giving incorrect results.
Resolution: Fixed.
MIPRO-49806
The MWS file with an empty BitMap XML element created with MapXtreme Workspace manager,
fails to open in MapInfo Pro.
Resolution: Fixed.
MIPRO-43994
In some cases, MapInfo Pro does not show any data for columns type nchar and nvarchar
from SQL Server tables.
Resolution: Fixed.
MIPRO-56808
MIPRO-56815
Release Notes
14
Issue Number
MIPRO-57147
Certain transparent bitmap fill patterns did not print properly. The output of certain patterns
looks slightly different when printed due to the addition of extra pixels in the bitmap pattern.
This is most noticeable with region fill patterns B4, D4, and C5.
Resolution: Fixed.
MIPRO-14837
MIPRO-47349
MIPRO-44246
MIPRO-41963
MIPRO-22607
MapInfo Pro crashes when exporting or printing a map or a layout with a map that contain
polygons with holes.
Resolution: Fixed.
MIPRO-58031
Release Notes
15
Issue Number
MIPRO-57947
L10N: German: "Create Legend" dialogue - wild card not getting expanded
The wildcard strings # and % are used to insert map layer name and legend symbol type
into legends. They used to be stored in mires.dll string resources but have been moved out
to avoid being inadvertently translated.
MIPRO-57366
MIPRO-57872
MIPRO-58278
An error occurs in some non-English locales when processing a Workspace with minimized
or floating windows.
Resolution: Fixed.
MIPRO-55155
"Clear Map Objects Only" command is missing on the Ribbon interface. The functionality was
missing in MapInfo Pro 12.5.1, but it is now integrated on the Ribbon interface.
Resolution: Fixed. Now, the command "Clear Map Objects" is available on the TABLE and
the SPATIAL tab in the Edit group.
MIPRO-57300
Layout Designer text frames are too small, causing text to wrap onto the second line.
When opening a Workspace with a Layout Designer window, there are times when text frames
in the Layout Designer are not wide enough, which can cause some of the text to wrap down
onto the second line. Previously, the only work-around was to use the mouse to manually
resize such text frames to be wider.
Resolution: Fixed. Now when you open the Workspace, the text frame is wide enough to
avoid unintended text wrapping.
Release Notes
16
Issue Number
MIPRO-53676
Polygon Select tool selects outside the polygon if the polygon was not closed by the user.
Resolution: Fixed. Now, if the user forgets to close the polygon the application adds the last
segment automatically to close the polygon.
MIPRO-57784
Bing license gets corrupted and stops working after upgrading OS from Windows 8 to Windows
8.1.
Resolution: Fixed. Now, Bing licenses are unaffected by the OS upgrade.
Release Notes
17