Changes between Initial Version and Version 1 of Ticket #16580


Ignore:
Timestamp:
2018-08-07T20:02:47+02:00 (7 years ago)
Author:
Don-vip
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16580 – Description

    initial v1  
    1 The wiki says the following on the default values (explicitly set and implied):
     1TaggingPresets#Attributes says the following on the default values (explicitly set and implied):
    22
    3  default="default_value"
    4     An explicitly declared default value for the item. This value is only applied through a preset when the object the preset is applied to has zero keys. If a value for default is not given, different implied default values apply depending upon the type:
    5 
    6         <check> (whether a checkbox is ticked on or off by default): implied default is "off"
    7         <text>, <combo>, <multiselect>: implied default is "" 
     3 default="default_value"::
     4  An explicitly declared default value for the item. This value is ''only'' applied through a preset when the object the preset is applied to has ''zero keys''.
     5  If a value for default is not given, different implied default values apply depending upon the type:
     6  * <check> (whether a checkbox is ticked on or off by default): implied default is "off"
     7  * <text>, <combo>, <multiselect>: implied default is ""
    88
    99However the actual JOSM behaviour seems to be to assume undefined / "" for <check> elements and not the default value for the "off" state ("no").