Location field: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
<div align="right"><small>''« as of 2016-08- | <div align="right"><small>''« as of 2016-08-29, editions Mobile 3.9.7, Desktop 1.0.3 »''</small></div> | ||
----- | ----- | ||
A Location field may contain a location, depicted as a latitude/longitude pair of integers. | A Location field may contain a location, depicted as a latitude/longitude pair of integers. | ||
Line 30: | Line 30: | ||
; Dependencies : Ability to add one or more visibility dependencies upon fields with qualifying types. | ; Dependencies : Ability to add one or more visibility dependencies upon fields with qualifying types. | ||
[[Category:Spec]] |
Revision as of 00:29, 29 August 2016
« as of 2016-08-29, editions Mobile 3.9.7, Desktop 1.0.3 »
A Location field may contain a location, depicted as a latitude/longitude pair of integers.
A Location may be established as the current location or one obtained by pointing to a place on a map.
A Location may have an associated text field containing a postal address.
A Location field value is exported & imported as two integers (a latitude & a longitude) separated by a comma & space (", ").
Name and Hint
Standard across all field types.
Advanced Parameters
- Rapid determination of coordinates
- Choose between rapid action and higher accuracy.
- Separate field for the address
- By default, there is none; otherwise, either a name or a purpose may be specified.
- Required
- Make entry of a value mandatory before saving an entry
Display Options
- Display in the list as
- Select among the following roles for the current field:
- As a Regular field
- As an Entry Name
- As an Entry Description
- As an Entry Status
- Display field name in Entry Edit Card?
- By default, yes.
- Dependencies
- Ability to add one or more visibility dependencies upon fields with qualifying types.