Modify

Ticket #4532 (closed defect: worksforme)

Opened 2 years ago

Last modified 16 months ago

Munging around with multiple layers erased my command history

Reported by: avar Owned by: avar
Priority: major 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

no-command-history.png Download (305.8 KB) - added by avar 2 years ago.
JOSM with pending uploads but no command history

Change History

Changed 2 years ago by avar

JOSM with pending uploads but no command history

comment:1 follow-up: ↓ 2 Changed 2 years ago by mjulius

Should the command history be layer specific?

comment:2 in reply to: ↑ 1 Changed 2 years ago by avar

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 Changed 17 months ago by stoecker

  • Owner changed from team to avar
  • Status changed from new to needinfo

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

comment:4 Changed 16 months ago by stoecker

  • Status changed from needinfo to closed
  • Resolution set to worksforme
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'reopened'
Author


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

 
Note: See TracTickets for help on using tickets.