Be smarter about excluding duplicates from the JOSM selection (and maybe search?) stack
|Reported by:||avar||Owned by:||team|
Description (last modified by simon04)
A frequent use case of mine with JOSM goes like this:
- Load up a large pile of data
- Select an area on it
- Execute a complex "selected ..." search query
- Get maybe 100-200 ways I want to work on.
So far so good, then I zoom on one of the objects in the selection stack, edit it and then select the 200 ways back from the stack.
The problem is that as I'm going "one way -> edit -> 200 ways -> one way -> edit -> 200 ways -> ..." with my selection the selection with the 200 ways will eventually fall off my stack. This seems to be because JOSM will not add something new if it's already on the stack.
Instead what it should do is remove it from wherever it is now on the stack and put it in the front (the top). Then I could edit like this for hours without having to again zoom out and execute the initial search query.