Opened 13 years ago
Closed 12 years ago
#7323 closed defect (duplicate)
Inconsistent behaviour of tag value editor for number
Reported by: | Zverikk | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
When tag value is a number with two or more digits, it is selected when editor dialog opens. When it's a single digit, it is not selected. Which is very inconvenient: when I want to replace a value with another, I always have to check whether the previous value is selected, or I have to press backspace to erase it.
The same inconsistency is present when adding a new tag: if it was a large number, it is preserved from the last time a tag was added, but if it is a single digit, it is erased. I was against preserving values at all, but if we do, please make it consistent: I use this functionality now for copying the last tag onto a new object, but as in previous case, must check if it was a single- or a multiple-digit number.
Attachments (0)
Change History (4)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
comment:3 by , 12 years ago
i have to say this is highly annoying and i repeatedly make mistakes - i just hope i spot them...
for example, adding data today my workflow was like this :
select building, alt+a, addr:housenumber=13, addr:street=blah
select building, alt+a, addr:housenumber=15, addr:street=blah, building:levels=1
select building, alt+a, addr:housenumber=117, addr:street=blah...
having a single digit not being selected is mighty bad :)
comment:4 by , 12 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
This is on purpose. There were problems with autocompletion and offering the last entered value. Have to dig deeper as this was implemented some time ago.