Changes between Version 156 and Version 157 of TaggingPresets

Timestamp:

2020-03-31T03:14:03+02:00 (6 years ago)

Author:

skyper

Comment:

added ticket link to broken "editable"

TaggingPresets

@@ -163 +163 @@
   Whether the off value of a `<check>` is disabled in the dialog, i.e., only unset or `"yes"` are provided.
  editable="false"::
-  The combo box is read only, which means that the user can only select an item in the list. Default is `"true"`, which means, the user can add other values as text.
+  The combo box is read only, which means that the user can only select an item in the list. Default is `"true"`, which means, the user can add other values as text. **Feature is broken see #6157**.
  use_last_as_default="true|false|force"::
-  For `<combo>`, `<multiselect>` or `<text>` fields the last value is used as default. Using `"force"` enforces this behaviour also for already tagged objects. Default is `"false"`.
+  For `<combo>`, `<multiselect>` or `<text>` fields the last value is used as default. Using `"force"` enforces this behavior also for already tagged objects. Default is `"false"`.
  rows="count"::
   Specify the number of rows to display in `<multiselect>` entry (if not set, it is auto determined by java or the look and feel and results in e.g. 8).