This list of versions and their associated release notes is intended to help users decide if/when it is appropriate for them to update MobileMap to take advantage of new features or bug fixes.
Table of Contents |
---|
MobileMap 4.4.
...
31
Photos
Fixed bug that caused crash when MobileMap resumed after taking a picture AND the device was in a different orientation (portrait/landscape) from when the photo was initiated.
MobileMap 4.4.30 (Beta)
Tree List
Decreased button widths on Tree List popups to fix issue on Nautiz X6 units where buttons extended off of screen to left and right. Specifically, decreased width of Clear, Cancel and Done buttons on the select_domain_value_layout to match button width on non_domain_popup_layout and decreased the capitalization button "Aa" on non_domain_popup_layout (from 100dp to 50dp).
Read-Only Logic
Added support for 'IN' operator in Tree Read-Only Logic. This allows for more than 1 value in a single attribute field to be used to set an existing tree record to read-only on Tree List load. This change was requested by WeyCo R&D so that several different tree status values could be used simultaneously to indicate that a tree should be read-only.
Related Tables
Minor update to Related Tables to ensure that functionality matched setting description. In previous release (4.4.29) the target field and value inputs had been swapped
MobileMap 4.4.29
Photos
Added support for writing metadata into photos as a watermark, with white text on a semi-transparent gray block at either the top or bottom of the image. User can select to add the current date, time, GPS coordinates, device orientation (azimuth) and any attribute field that is present on the parent feature. The user can also select the font size to be used. MobileMap will determine the size of the watermark and the number of columns based on the number of metadata fields and font size. Relevant settings are in Settings > Photos > Photo Watermarks.
Related Tables
Added Related Tables Logic setting (Settings > Data Model > Related Tables Logic) that enables automated population/update of attribute(s) in the parent record based on attributes in the child record(s). Allows users to define one or more logic statements for each child table. When child table loads, or is refreshed after closing a child record. Logic tests compare a child attribute to a value or theshold. If any records pass this test, then the second part of the logic kicks in and updates the parent attribute with either a fixed value (e.g., '2' or 'Yes') or a value from the first child record that met the logic test. Assumes that if the target field (in the parent record) is a coded value domain then the source field should also be a coded value domain with the same domain values.
...