Opened 15 years ago
Closed 15 years ago
#4593 closed defect (fixed)
conflict list and header not updated right away after undo/redo
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | conflict list header | Cc: | skyper |
Description
The conflict list is not updated right away. After solving a conflict you need to do one more action (select for example) to have the conflict list updated.
The total number in the header does not change at all.
Attachments (1)
Change History (26)
follow-up: 4 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Keywords: | r-2010-01-blocker removed |
---|
comment:4 by , 15 years ago
Replying to bastiK:
What josm version?
version 3029 and 3033
I addressed this issue recently; try latest.
what changeset ?
I will try.
comment:5 by , 15 years ago
in [3016].
If there is still a missing update of the entire dialog, please describe how to reproduce.
(The header issue is not fixed jet.)
comment:6 by , 15 years ago
Keywords: | header added |
---|---|
Summary: | conflict list not updated right away → conflict list header(was: conflict list not updated right away) |
Works all for me with sun, have to check openjdk
follow-up: 10 comment:8 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
@skyper: Please add the josm version for every bug report! It makes live so much easier for us.
comment:10 by , 15 years ago
Replying to anonymous:
@skyper: Please add the josm version for every bug report! It makes live so much easier for us.
I did this time. - Maybe we should not provide latest in the bug report but the version !!!.
So far I first look at the main page to get to know if there is a new release and then write my bug-report. On the web-interface the report-time is a link that you can see what has been done that day and what version latest really was.
Anyway I was wrong:
Sorry, it did work with conflicts resulting of a merge (downloaded the same area again on same layer). Header list does not update if the conflicts arise after "update data".
still version 3040, sun-java 6 on ubuntu karmic (9.10)
comment:11 by , 15 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:12 by , 15 years ago
Summary: | conflict list header(was: conflict list not updated right away) → conflict list not updated right away and conflict list header not updated at all |
---|
Sorry, the list is not update right away, as I mentioned above the list-update takes one more action in between.
I forgot to mention that I have updated the plugins in between, but I do not know if there were any differences because of #4565.
comment:13 by , 15 years ago
Priority: | normal → major |
---|
comment:14 by , 15 years ago
Works for me: Update data -> conflicts. Resolve one conflict -> header and content changes.
Please give a step by step description (and maybe an *.osm file to load).
comment:15 by , 15 years ago
This is still broken on r3056. Here's how I (approx) ran into it:
- Edit a day-old country dump
- Merge 10 consecutive ways into 1
- Change its highway=* tag
Meanwhile on the server someone had done this before me:
- Edit a day-old country dump
- Don't merge these ways
- Change their highway=* tag and add FIXME=*
Any conflict resolution that I do makes the dialog not update when it's changed. I'm attaching a video showing this.
by , 15 years ago
Attachment: | test-0000.mpeg added |
---|
Video showing conflict resolution dialog failing to update
comment:16 by , 15 years ago
Also please add the r-2010-01-blocker keyword back, this is definitely a regression from the previous release and makes any conflict resolution very hard. I don't think a release should go out with this bug.
comment:17 by , 15 years ago
I concur with the header not updating. I just had 2 conflicts, and the header still showed 'Conflicts: 2 unresolved' after resolving those. Then I had another single conflict, and while that showed in the list, the header still showed the 2.
As for the contents: when I get a single conflict, it pops up right away in the list, but if I have 2 or more conflicts, they don't appear in the conflicts list. I have to close and reopen (Alt+C) to see them.
JOSM 3044 + Sun JDK (WinXP)
follow-up: 20 comment:19 by , 15 years ago
This might help. (But I still cannot reproduce.) Additionally, it should now print something to the command line each time you resolve a conflict. (If not, something is wrong.)
Anyway, can you attach a osm file where you always get this behaviour? This would help a lot.
follow-up: 21 comment:20 by , 15 years ago
Replying to bastiK:
This might help. (But I still cannot reproduce.) Additionally, it should now print something to the command line each time you resolve a conflict. (If not, something is wrong.)
Anyway, can you attach a osm file where you always get this behaviour? This would help a lot.
I can't figure out how to not reproduce this. Anyway here's how (on a version before your fix, I didn't test that out):
- Download http://osm.nix.is/archive/2010-02-01/Iceland.osm.bz2
- Search for id:48322685
- Zoom out and select that entire area
- Search for parent(selected type:node) "ofp:highway"=*
- This'll give you a bunch of ways with ofp:highway=*
- Set tags like foo=bar test=yest blah=blah on the objects
- Upload, get conflicts
- Sync way X only
- Conflict dialog doesn't update
- Prod it, now it does
- Change some more data, try this again
- Conflict count doesn't update until you minimize / maximize the conflict panel
comment:21 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
follow-up: 23 comment:22 by , 15 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Summary: | conflict list not updated right away and conflict list header not updated at all → conflict list and header not updated right away after undo/redo |
It is not quite done yet.
I solve a conflict and press undo -> conflict list is empty, minimize and maximize gets it back.
I press redo -> the list does not change at all. Again mini- and maximize will do it.
r3057 with openjdk
comment:25 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
What josm version?
I addressed this issue recently; try latest.