You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
On top of that, it should always trim spaces at the start and at the end of a key or value string.
I'd suggest to render "(new tag)" and "(new value)" in italic font and not count it as a tag change unless both fields have been edited. It shouldn't be necessary to initialize the cell editor with this placeholder string because you never enter something ot that kind.
Why not rename "(new tag)" --> "(new key)"?
(Used the Potlatch 2 version that
The text was updated successfully, but these errors were encountered:
Author: Richard [Added to the original trac issue at 7.21pm, Tuesday, 4th January 2011]
This should be fixed in r24973. The UI isn't particularly elegant if you try and blank a key (the DataGrid row sticks around until you select another entity) but unfortunately my poor brane gets confused when faced with DataGrid events and the tag architecture and wotnot.
Reporter: sebastiank
[Submitted to the original trac issue database at 10.38pm, Friday, 3rd December 2010]
It shouldn't be possible to create a tag with either key or value is the string of length 0.
(See http://www.openstreetmap.org/browse/node/1019041185/history for an example.)
On top of that, it should always trim spaces at the start and at the end of a key or value string.
I'd suggest to render "(new tag)" and "(new value)" in italic font and not count it as a tag change unless both fields have been edited. It shouldn't be necessary to initialize the cell editor with this placeholder string because you never enter something ot that kind.
Why not rename "(new tag)" --> "(new key)"?
(Used the Potlatch 2 version that
The text was updated successfully, but these errors were encountered: