Modify

Ticket #4998 (new defect)

Opened 2 years ago

Last modified 2 years ago

Impossible to select nodes with filter

Reported by: stoecker Owned by: team
Priority: major Component: Core
Version: Keywords:
Cc:

Description

When e.g. a street and a languse overlap using the same nodes, then it is impossible to select one of the nodes when languse is filtered. Always the whole way is selected.

It seems nodes of filtered objects aren't taken into account for selection even if they are also unfiltered.

Probably they should be a warning (e.g. in filter display), but they should be selectable.

Attachments

Change History

comment:1 Changed 2 years ago by bastiK

I guess you have "apply also for children" checkbox ticked. Then these nodes are indeed filtered and this is the expected behaviour.

But it shouldn't be like this. First it's not good to put both, "nodes of a way" and "members of a relaion", in one option. I don't think we need the latter option at all, because it might cause confusion more often than it is useful. And it can be easily simulated with search patern like child (type:relation boundary=administrative).

I'd suggest to remove the "C" option completely and apply sensible default behaviour instead:

  • If a way is not filtered, all its nodes are not filtered.
  • If a way is filtered, all untagged nodes are filtered as well, unless the first rule applies.
  • If a filter applies explicitly for a node then forget about the first two rules and filter it.

comment:2 Changed 2 years ago by stoecker

Suggestion sounds good to me.

comment:3 follow-up: ↓ 4 Changed 2 years ago by stoecker

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

comment:4 in reply to: ↑ 3 Changed 2 years ago by anonymous

Replying to stoecker:

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

Suggestion from the ticket

To prevent false moved nodes, the position should be locked (e.g. marked as red x). If you want to delete the node, it should only be removed from the displayed ways and disappear. (but not be deleted)

comment:5 Changed 2 years ago by stoecker

  • Priority changed from normal to major

comment:6 Changed 2 years ago by bastiK

(In [3300]) see #4998 - Impossible to select nodes with filter

comment:7 Changed 2 years ago by bastiK

First attempt to fix this. It should cover the basic cases but definitely needs some testing.

I think for the search modes 'remove' and 'find in selection' it is not optimal yet (shows superfluous nodes). But I have problems to imagine what these are used for so better hide too view than too much.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will be changed from team. Next status will be 'new'
Next status will be 'needinfo'The owner will change to stoecker
as duplicate The resolution will be set to duplicate. Next status will be 'closed'The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous. Next status will be 'assigned'
Author


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

 
Note: See TracTickets for help on using tickets.