Modify

Opened 15 years ago

Closed 15 years ago

#4532 closed defect (worksforme)

Munging around with multiple layers erased my command history

Reported by: avarab@… Owned by: avarab@…
Priority: major Milestone:
Component: Core Version: latest
Keywords: Cc:

Description

I:

  1. Downloaded http://osm.nix.is/latest/Iceland.osm.bz2
  2. Connected some ways, removed some etc.

At this point I still had a command history. But then I thought I might have accidentally deleted some data that I wasn't finding with the search engine (it turned out I didn't delete it) so I:

  1. Opened the download dialog
  2. Downloaded a portion of Iceland as a new layer
  3. Downloaded some more into that new layer

Then after reviewing it I:

  1. Switched back to the original Iceland.osm layer

Now I have pending uploads in Iceland.osm but no command history, see the attached screenshot.

Attachments (1)

no-command-history.png (305.8 KB ) - added by avarab@… 15 years ago.
JOSM with pending uploads but no command history

Download all attachments as: .zip

Change History (5)

by avarab@…, 15 years ago

Attachment: no-command-history.png added

JOSM with pending uploads but no command history

comment:1 by mjulius, 15 years ago

Should the command history be layer specific?

in reply to:  1 comment:2 by avarab@…, 15 years ago

Replying to mjulius:

Should the command history be layer specific?

That would be helpful yes. Ideally the command history would also not be a stack so you could selectively undo things but that's another issue.

comment:3 by stoecker, 15 years ago

Owner: changed from team to avarab@…
Status: newneedinfo

We have layer specific history now. Can you reproduce this report today?

comment:4 by stoecker, 15 years ago

Resolution: worksforme
Status: needinfoclosed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain avarab@….
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.