Changes between Version 153 and Version 154 of TaggingPresets
- Timestamp:
- 2020-03-19T18:38:42+01:00 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TaggingPresets
v153 v154 43 43 44 44 === Tags === 45 ==== The document prolog ==== 45 ==== The document prologue ==== 46 46 <presets>:: 47 47 Has to be the main tag of the file. Supports following attributes 48 48 * '''xmlns="http://josm.openstreetmap.de/tagging-preset-1.0"''' 49 49 * '''author''' - the name of the author of the preset 50 * '''version''' - the version number of the file. For automatic alversion adjustment of presets managed in this wiki you can use two internal variables: `[[revision]]` (the latest version number of the wiki page) and `[[date]]` (the date of the last edit).50 * '''version''' - the version number of the file. For automatic version adjustment of presets managed in this wiki you can use two internal variables: `[[revision]]` (the latest version number of the wiki page) and `[[date]]` (the date of the last edit). 51 51 * '''description''' (i18n) - description what the file contains 52 52 * '''shortdescription''' (i18n) - very short overview description i.e. the "name" of the preset … … 103 103 <combo>:: 104 104 Displays a multiple choice combo box. `key` and `values` are mandatory, `text`, `default`, `editable`, `delimiter`, `values_from`, `display_values`, `short_descriptions`, `use_last_as_default`, `values_searchable`, `length`, `values_no_i18n`, `values_sort` and `match` is optional.\\ 105 If editableis `"true"` (default), combo boxes can be edited as if they were text fields (additional to the drop down menu). Non editable combo boxes can only contain one of the specified values.105 If `editable` is `"true"` (default), combo boxes can be edited as if they were text fields (additional to the drop down menu). Non editable combo boxes can only contain one of the specified values. 106 106 <multiselect>:: [=#multiselect] 107 107 Displays a list from which zero or more items can be chosen. `key` and `values` are mandatory, and `text`, `default`, `delimiter`, `values_from`, `rows`, `display_values`, `short_descriptions`, `use_last_as_default`, `values_searchable`, `values_no_i18n`, `values_sort` and `match` are optional. The selected values will be concatenated with the specified delimiter (default: semicolon) and written to the tag value. If a tag value has already been set when the preset dialog is opened, the `<multiselect>` will attempt to mark the appropriate items in the list as select. If the tag value cannot be represented by a combination of choices in the list, then the list will be disabled so that the user cannot accidentally overwrite a custom value. In contrast to the `<combo>` element, the `<multiselect>` expects the list of values, descriptions etc. to use the specified delimiter, i.e. by default you will have to use a semicolon. You can specify `delimiter=","` but then a comma will also be used in the tag value. 108 108 <list_entry>:: 109 Used in <combo> and <multiselect>. More information see `short_descriptions`. The attributes are `value`, `display_value`, `short_description`, `icon` and `icon_size`. 109 Used in <combo> and <multiselect>. More information see `short_descriptions` [#short_description below]. The attributes are `value`, `display_value`, `short_description`, `icon` and `icon_size`. 110 110 <check>:: 111 111 A checkbox which the user can select, deselect or set as unset. The `key` attribute is mandatory. `text`, `default`, `match`, `value_on` , `value_off`, `disable_off`, `icon` and `icon_size` (both since r15437) are optional. … … 204 204 delimiter="special character":: 205 205 The character that separates values. In case of `<combo>` the default is ''comma''. In case of `<multiselect>` the default is ''semicolon'' and this will also be used to separate selected values in the tag. More information see `<multiselect>` [#multiselect above]. 206 short_descriptions="Entry1,Entry2,Entry3":: 206 short_descriptions="Entry1,Entry2,Entry3":: [=#short_description] 207 207 A delimiter-separated list of texts to be displayed below each `display_value`. (Only if it is not possible to describe the entry in 2-3 words.) Instead of comma separated list instead using `values`, `display_values` and `short_descriptions`, the following form is also supported: `<list_entry value="" display_value="" short_description="" icon="" icon_size="" />` 208 208 values_searchable="true|false"::
