Filtered and disabled objects can be selected

[bundesrainer]

When using the filter function, filtered objects are grayed out and can not be selected by clicking. But when I mark an area (Click + Hold) the filtered objects are also selected.

[bastiK]

Why is it critical? The objects are selected and filtered. It's not nice but it doesn't cause data corruption or something like that.

Note that there are other ways to get this situation:

• select something, then change the filter to include these objects

• use selection history

• undo, such that the properties of a selected change and a filter applies

[bastiK]

(In [3198]) see #4929 - rectangle selection selects filtered objects.
(the other things mentioned in this ticket are not addressed)

[bastiK]

(In [3199]) see #4929 - filtered objects can be selected: fixed the first and the third issue from my reply (select something, then change the filter to include these objects; undo, such that the properties of a selected change and a filter applies)

[bastiK]

What shall we do for search? There should be a dialog box or a popup message to inform the user that more was found, but could not be selected because of active filters.

[stoecker]

Why set as critical: Because the biggest problem I have with filtering is the fact that users may destroy valid data. This also was the reason why the filter was disabled by default for so long. As you fixed major issues I change it to major.

About "use selection history": We can delete it when filters are applied or changed.

[bastiK]

About "use selection history": We can delete it when filters are applied or changed.

This would certainly annoy some users, including me. Another solution would be to purge the chosen selection like it needs to be done for deleted objects (?) and change the text in the popup menu to include the number of currently filtered/disabled (if any).

[extropy]

Cannot reproduce this on Version 3329.
Is this fixed?

[bastiK]

Remaining issues:

(a) 'search' results in filtered objects being selected
(b) search history allows filtered objects to be selected
(c) command stack select tool allows the same

I'm no longer sure, these are real issues. With respect to #5144 we should treat selected and filtered objects as if they weren't filtered.

[stoecker]

Good idea (but I see another bunch of possible bug reports). Let's try it and see what the result is.

[skyper]

Ticket #7238 has been marked as a duplicate of this ticket.

[openstreetmap.org-user-d1g]

Untested

Replying to bastiK:

(b) search history allows filtered objects to be selected

1. missing activation in command history

Replying to bastiK:

(c) command stack select tool allows the same

Yes, it is possible to select, otherwise filtered objects in command history using right click menu.

Either solution would be okay:

• display "Unselectable now" message, suppress right click menu
• display object, add "currently filtered out" in node/way/relation caption, disable respective item in right click menu

2. missing activation in in-line editor

Replying to bastiK:

• select something, then change the filter to include these objects

Doesn't work with in-line editor (but "edit" button is respected):

1. add filter natural=* (auto enabled by JOSM)
2. focus text in "Text" column, change natural=* to natural=tree (or rock)
3. hit Enter

Filtered objects are not updated, but they should (it will actually work with Edit button)

3. works for me

Replying to bundesrainer:

But when I mark an area (Click + Hold) the filtered objects are also selected.

Not in r11223.

Select all won't select them too.

Replying to bastiK:

• use selection history

It will show "Unselectable now" message

Replying to bastiK:

• undo, such that the properties of a selected change and a filter applies

filters respected well, when you add tags using history: Ctrl+Z Ctrl+Y

Replying to bastiK:

(a) 'search' results in filtered objects being selected

In r11223 I tried to search for natural=tree when they were filtered out, I got "no match for 'natural=tree'" message.