Ticket #4532 (new defect)

Opened 6 months ago

Last modified 5 months ago

Munging around with multiple layers erased my command history

Reported by: avar Owned by: team
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 6 months ago.
JOSM with pending uploads but no command history

Change History

Changed 6 months ago by avar

JOSM with pending uploads but no command history

follow-up: ↓ 2   Changed 5 months ago by mjulius

Should the command history be layer specific?

in reply to: ↑ 1   Changed 5 months 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.

Add/Change #4532 (Munging around with multiple layers erased my command history)

Author


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


Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from team. Next status will be 'new'
Next status will be 'needinfo'The owner will change to avar
as duplicate The resolution will be set to duplicate. Next status will be 'closed'The specified ticket will be cross-referenced with this ticket
The owner will change from team to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.