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.
Reporter: LonelyPixel [Submitted to the original trac issue database at 7.13pm, Friday, 9th January 2009]
One of the most annoying things to me in Merkaartor is that when I
select two objects (one after another) to compare their tags, they
always are in a different order. It's hard to tell quickly whether they
have the same tags and values assigned. The only solution to this is to
sort the tags in the list. This is what my patch does. It may not be the
most efficient sorting algorithm, in fact it's the first I was thinking
of, to sort the items in-place. It is working fine for me, I could not
determine any data corruption in a small test and it doesn't lead to a
sensible delay. (How could that be for a list of < 10 items...)
Maybe this could be improved by applying a certain pre-defined order
different from the lexical. For example: highway < service < name <
maxspeed < * < note < created_by. That would be more of an order by
importance first, then tag name.
The text was updated successfully, but these errors were encountered:
Reporter: LonelyPixel
[Submitted to the original trac issue database at 7.13pm, Friday, 9th January 2009]
One of the most annoying things to me in Merkaartor is that when I
select two objects (one after another) to compare their tags, they
always are in a different order. It's hard to tell quickly whether they
have the same tags and values assigned. The only solution to this is to
sort the tags in the list. This is what my patch does. It may not be the
most efficient sorting algorithm, in fact it's the first I was thinking
of, to sort the items in-place. It is working fine for me, I could not
determine any data corruption in a small test and it doesn't lead to a
sensible delay. (How could that be for a list of < 10 items...)
Maybe this could be improved by applying a certain pre-defined order
different from the lexical. For example: highway < service < name <
maxspeed < * < note < created_by. That would be more of an order by
importance first, then tag name.
The text was updated successfully, but these errors were encountered: