All Wrapper files are zipped into one small file for download. The file name indicates the revision date.
When you unzip the file, be sure to "Use Folder Names" so that sample API code is placed in a separate directory named samplecode. You must also "Use Folder Names" so as not to overwrite one of the two 00readme.txt files.
After downloading and unzipping the ZIP file, check to be sure
the files include a separate directory named samplecode.
If not, delete the files and unzip again, making sure to specify "Use Folder Names" or equivalent in your ZIP software.
November 3, 2009 release - mgMWFwrapper20091103.zip
- Check for Windows 7 in addition to other OS's and treat the same as Vista.
- Add check for 64-bit Internet Explorer on Windows and tell user to use 32-bit Internet Explorer.
January 28, 2008 release
- Add support for new onunload URL parameter as well as support for picking up an optional onunload value from a JavaScript variable if not defined on the URL. This allows defining the onunload value in API code. It works like the existing onload parameter and JavaScript variable but specifies text to be included in the map frames <body> tag onUnload parameter to specify processing to be done when the map window is closed. This was added to allow API code to close child windows opened during the map session.
October 16, 2007 release
- Check for Windows Vista in addition to Windows XP for issuing the installation security popup message that was unique to Windows XP but is now displayed for both Windows XP and Windows Vista.
- Added test to detect if user is using Safari. The Wrapper itself has no need for this at this time, but we test for it now to make the result available for site-specific code.
June 8, 2007 release
- Added support for the MapGuide Viewer version 6.5SP1.
- Adjusted MapGuide Viewer CAB file locations in mgmapsettings.inc since Autodesk removed older CAB files on their server at www.mapguide.com/Downloads/. These use the Pima County website for CAB files that are not available from Autodesk. Please put the mgaxctrl.cab files on your server and reference your server locations in mgmapsettings.inc rather than using Pima County and Autodesk servers.
- Added test to detect if user is using Firefox. The Wrapper itself has no need for this at this time, but we test for it now to make the result available for site-specific code.
May 3, 2006 release
- Replaced loading the Viewer ActiveX control directly with an external InsertControl function. This automatically enables the control and avoids "Click to activate and use control" with Microsoft's 4/2006 patches to Internet Explorer. If the user has cleared the "Disable Script Debugging" Internet Explorer option on the Advanced Tab under Tools, Internet Options then they will continue to see "Click to activate and use control" and have to click. See Autodesk Knowledgebase document TS1056367 and the MSDN article Activating ActiveX Controls.
February 25, 2006 release
- Added mgobjectlinktarget and mgreporttarget settings to provide default override of objectlinktarget and reporttarget URL parameter values. (objectlinktarget and reporttarget are standard MWF URL parameters defined by Autodesk.)
- Changed mgmap.cfm to code HTML directly rather than with JavaScript document.write as document.write was no longer required by the Wrapper design. There is no change to mgmap.cfm use or function.
January 23, 2006 release
This release was mostly cleanup. There is no significant new function.
- Added new mgmapviewerobjectname setting in mgmapsettings.inc so API developers can control the Viewer object name in the generated map OBJECT, EMBED or APPLET tag. The default 'myMap' was previously hard coded.
- Added new titleframeheight URL parameter to allow overriding the default 40 pixel title frame height for applications that need it.
- Added scope to all ColdFusion variables that weren't scoped for clarity and efficiency.
- Fixed missing slash on closing BODY tag in mgmaptitleframe.cfm
- Removed most documentation from code headers. Wrapper documentation is now only on these web pages.
- Removed the last traces of code specific to Pima County.
August 31, 2005 release
- Adjusted MapGuide Viewer CAB file locations in mgmapsettings.inc since Autodesk moved or removed older CAB files on their servers.
August 18, 2005 release
- No functional changes or bug fixes in this release.
- Used more appropriate and generalized sample settings in mgmapsettings.inc
- Minor text file and code comment updates.
May 26, 2005 release
- First version available for download on the Internet after over a year of use by Pima County and others.
Pima County MapGuide MWF Wrapper Main Page