#15620 closed defect (fixed)
[patch] select previous gap (or next gap) may lead to an invisible selection in the member table
Reported by: | cmuelle8 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 17.12 |
Component: | Core | Version: | |
Keywords: | relation editor gap | Cc: |
Description
Symptom:
Selection not shown after action is used.
Reason:
The result of the select (previous, next) gap actions may be
a selected element outside the viewport of the MemberTable.
Solution:
This patch fires the proper event to ensure that the part of
the member table becomes visible that holds the selection.
Attachments (1)
Change History (5)
by , 7 years ago
comment:1 by , 7 years ago
Keywords: | relation editor gap added |
---|---|
Milestone: | → 17.12 |
comment:2 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 by , 7 years ago
Replying to Don-vip:
thanks!
no problem, please consider the other (recent) patches as well,
once you have finished reviewing them.
I'm pretty confident for
- the smaller one in ticket:15574
- it will reduce that ticket, so that the portion left will better match the ticket title
- the smaller patch attachment is an excerpt of the larger, that is more closely related to ticket:15476 actually
- ticket:15606
I'm somewhat confident for
- attachment:josm-joinAreasAction-minimal-set-of-boundaries.patch:ticket:14528
- it is not an overall solution to the existing problems nor an overhaul of the complete joining code
- it won't make things worse for ticket:14528 and ticket:10511
- but does not fix ticket:10511 (yet, I may have another look at that within the scope of the old code)
I still did not rework
- ticket:12420 that got lost in the way
- needs expert config option
- should be enabled only in expert mode
In 13176/josm: