Modify

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#12554 closed enhancement (fixed)

Disable storing last used values for some tags

Reported by: Zverikk Owned by: team
Priority: normal Milestone: 16.04
Component: Core Version: latest
Keywords: Cc:

Description

Some tags, like roof:colour, or addr:housenumber, or pk, or ref, rarely repeat, and just take up space in the last used tags list (in the tag editor dialog), which is quite short. Could you please make an option to exclude some keys from that list?

Attachments (1)

2016-03-06-171138_1200x1920_scrot.png (12.1 KB) - added by simon04 4 years ago.

Download all attachments as: .zip

Change History (19)

comment:1 Changed 4 years ago by Klumbumbus

you can change the number of displayed tags. see also #12438 for new option to hide already set tags.

comment:2 Changed 4 years ago by Zverikk

The idea is to keep the list small, by not showing key-value pairs that won't be used again. These pairs shift useful pairs off the list, so hiding them doesn't help.

comment:3 Changed 4 years ago by malenki

@Zverikk: Hiding the tags with "useless" values would sure help. ;)
Thanks for posting this ticket so I don't have to.

Last edited 4 years ago by malenki (previous) (diff)

comment:4 Changed 4 years ago by simon04

A criterion to decide "useless" keys/values without having to maintain yet-another key-list in the code is welcome :)

comment:5 Changed 4 years ago by malenki

@simon04: I would be satisfied with a filter the user can configure to his own liking.

comment:6 Changed 4 years ago by Don-vip

Maybe only keys with values defined in presets?

comment:7 Changed 4 years ago by simon04

Or an ignore system similar to the validation errors: right click on a recent tag → "ignore key", "ignore tag"?

comment:8 in reply to:  6 Changed 4 years ago by malenki

Replying to Don-vip:

Maybe only keys with values defined in presets?

For housenumbers and colours this wouldn't work.
There is no addr:housenumber=77Q nor roof:colour=89ab12 and similar stuff set as preset.

comment:9 in reply to:  4 ; Changed 4 years ago by bastiK

Replying to simon04:

A criterion to decide "useless" keys/values without having to maintain yet-another key-list in the code is welcome :)

I don't think it is possible:

  • addr:street=* -> keep
  • addr:housenumber=* -> ignore
  • height=* -> keep (?)
  • ...

Replying to simon04:

Or an ignore system similar to the validation errors: right click on a recent tag → "ignore key", "ignore tag"?

Sounds good.

comment:10 in reply to:  9 Changed 4 years ago by Klumbumbus

Just a thought: even when tagging the same housenumber twice seems unlikely, I maybe want to see it in the list anyway, because I maybe want to click on it to set the key and just adjust the value. So user should decide, which tags he wants to hide.

Replying to bastiK:

Replying to simon04:

Or an ignore system similar to the validation errors: right click on a recent tag → "ignore key", "ignore tag"?

Sounds good.

yes.

comment:11 Changed 4 years ago by simon04

Milestone: 16.03

comment:12 Changed 4 years ago by simon04

In 9939/josm:

see #12554 - Factor out RecentTagCollection, add unit tests

comment:13 Changed 4 years ago by simon04

In 9940/josm:

see #12554 - Allow to ignore keys/tags from recent tags

Changed 4 years ago by simon04

comment:14 Changed 4 years ago by simon04


comment:15 Changed 4 years ago by malenki

Nice work – Thank you!

comment:16 Changed 4 years ago by Don-vip

is this fixed?

comment:17 Changed 4 years ago by Zverikk

Resolution: fixed
Status: newclosed

Yes.

comment:18 Changed 4 years ago by Don-vip

Milestone: 16.0316.04

Milestone renamed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.