Opened 13 years ago
Closed 13 years ago
#6652 closed defect (fixed)
[PATCH] Members list in history panel for relations and ways is broken
Reported by: | Zverikk | Owned by: | olejorgenb |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
- Select a relation with more than one version
- Open history panel and click "Show"
- Select "Members" tab
- Observe the left table. It shows one member all the way and has no sense.
Attachments (3)
Change History (8)
comment:1 by , 13 years ago
by , 13 years ago
Attachment: | josm-history-repeating.gif added |
---|
comment:2 by , 13 years ago
I've desribed the bug incorrectly. Actually, there are two list of nodes for a way (or nodes+ways for a relation) in history window, "Members" tab. They are always of the same size, regardless of actual number of nodes. Lists are padded with the last node ID, resulting in a sequence of repeating IDs, making no sense. Empty lines should be shown instead. Check right column on the screenshot.
comment:3 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Summary: | Members list in history panel for relations is broken → [PATCH] Members list in history panel for relations and ways is broken |
Patch attached.
PS: The node list for way-history has the same problem
Off topic: The HistoryBrowserModel has lots of code sections like this:
if (pointInTimeType.equals(PointInTimeType.CURRENT_POINT_IN_TIME)) { if (! current.getType().equals(OsmPrimitiveType.WAY)) return null; return (HistoryWay)current; } if (pointInTimeType.equals(PointInTimeType.REFERENCE_POINT_IN_TIME)) { if (! reference.getType().equals(OsmPrimitiveType.WAY)) return null; return (HistoryWay)reference; }
I think HistoryBrowserModel could be simplified a lot by adding a getTargetIfValid
method or maybe storing the target directly in the sub-models.
I could do something like that if it's not considered to much a case of "If It Ain't Broke, Don't Fix It"
by , 13 years ago
Attachment: | ticket-6652-last-member-repeated-in-history-diff.patch added |
---|
comment:4 by , 13 years ago
Ups, that approach screwed up the scrollbar sync. Better patch attached.
by , 13 years ago
Attachment: | ticket-6652-last-member-repeated-in-history-diff-v2.patch added |
---|
Could you attach a screenshot explaining the problem ? I don't understand your concern.