2.4.
...
Pending Release
Fixes
- Tooltip fix in redline.
- The tooltips for the redline stroke menu could not be set using i18n resources.
- WFS Fix.
- Extended attributes in WFS services were causing problems.
- Security bundle fix.
- The Acegi security bundle was exporting some incorrect metadata.
- Progress bar fixes.
- Some issues with progress bars not stopping have been addressed.
- Spelling mistakes.
- Some spelling mistakes in the handling of startup errors have been fixed.
- CoordZoom border fix.
- The CoordZoom dialog box had an extra border in the UI.
- Fixed 'pressed' handing in MapTips.
- The 'pressed' setting for the MapTips tool was not working properly.
- Geometry building code fix.
- The code to encode geometry for sending to the server was fixed and refactored so all routines use the same code.
- Toogle toolbar fix.
- An issue with the width of the toogle toolbars was fixed.
- Some minor fixes for ToC models on client.
- Some extra checks were added to the ToC UI code on the client to ensure robustness.
- Touch navigation was not enabled.
- The support for touch navigation of the map was not enabled.
- Fixed error reporting.
- Invalid component definitions in client config were not generating useful error messages.
- ArcGIS tile cache fix.
- An issue was fixed when using a subset of ArcGIS cache levels for client scales.
- Entity selector panel fix.
- Context menu tools were not working in the entity selector panel.
- Grid wrapping fix.
- Long items were not wrapping in the grid views.
2.4.26
Pending Release
Enhancements
- WMS scale adjustments.
- Some WMS services report their scale ranges based on a more rigid interpretation of the WMS specification, if you set adjustWmsScales to true in a server side map engine configuration it will take this into account when reporting the scale ranges to the client. This can be an issue because most WMS services seem to assume 96DPI when reporting scales ranges, but the spec says that it should be 90.7DPI, so if your client tool used to set the scale range is running an 96DPI and you set the scale to 10,000, the WMS server may tell Weave that the scale is actually 9447.916 (90.7/96*10000), so Weave need to undo this conversion to get back to the original value. So far Carmenta WMS server is the only one we've found with this issue.
- Zip'n'ship updates.
- The zip'n'ship client UI has been updated to be neater.
- The zip'n'ship client now has the option to enable/disable clipping and simplification of exported geometry.
- The zip'n'ship configuration now supports exporting layers directly, previously only entities could be exported.
Fixes
- 'pressed' not working for map tips.
- If 'pressed' is set to true in the map tips configuration the button is pressed but the map tips don't appear, if you turn the button off then on they then work correctly.
- ToC issues.
- Some minor issues with the client ToC code when things were mis-configured would stop the client from working.
- Uploaded files wouldn't re-project.
- File uploaded in a different projection would not be re-projected on the fly to the current map extent.
- Index search issue.
- The default wildcard search wasn't working properly, it would perform a fuzzy search instead, which could results not being returned when they should be.
- MIF driver fix.
- The MIF file driver was not handling geometry collections correctly.
- BIRT redline issue.
- Redlines were not drawn on a map embedded in a data set.
- Client startup error handling.
- Errors during client startup were not always providing enough information to diagnose the cause.
- Toggle toolbar issue.
- The width of toggle toolbar was incorrect in Internet Explorer.
- AGS server log issue.
- Spurious errors were being reported in the ArcGIS Server log when Weave tried to determine if caching was enabled for a map service.
- Comments in config file issue.
- Un-terminated or nested comments weren't being handled correcting in config files.
- Support dump missing files.
- The support dump tool was missing some startup and configuration files that should've been included.
- Spatial upload update.
- Memory mapped shapefile support was disables since it appears that it may have issues on Windows with large files.
- Shapefile driver update.
- The shapefile driver was not taking into account if the shapefile was remote when setting the memory mapped flag.
- Clipping updates for zip'n'ship.
- Sometimes the clipping of geometry exported by zip'n'ship wasn't working correctly.
- Index bundle compatibility fix.
- The index bundle was using an deprecated API call.
- Text wrapping in grid.
- The wrapping of text in grid panels has been restored after it was lost during the upgrade from Ext.js 2.2 to 2.3.
- Selection not drawing in report.
- A map embedded in a grid would not draw the selection properly.
- Tiled AGS layers fix.
- Configuring tiled AGS layers to not include some levels wasn't working.
- Updates for progress meter.
- Sometimes the progress meter wouldn't stop, this update attempts to resolve this.
- Touch navigation wasn't enabled.
- The support for touch navigation of the map was not enabled.
- Fix for BIRT reports.
- If a BIRT report uses a JDBC connection directly it was unable to locate the required JDBC drivers.
- Identify tool fix.
- The identify tool was not handling being set to use a point, as opposed to a circle, as the identify operation correctly.
- Informix SQL issue.
- There was a problem with the SQL generated by data definitions when run on an Informix database.
- WFS issue.
- A problem with parsing the capabilities document from some WFS servers was fixed.
- JDBC connector fix.
- There was no way to obtain a JDBC connection by code outside of the JDBC bundle.
- WMS re-scale fix.
- Adjustments to WMS map scales was being applied when using geographic coordinates which is shouldn't have been.
- AGS image server fix.
- AGS image service connections were failing.
- Security bundle fix.
- A enhancement to the security bundle wasn't being used because of a metadata error which has been fixed.
- Another security bundle fix.
- Some additional changes to the security bundle were required to fix support for other bundles to be able to perform authentication.