Modify ↓

Opened 9 years ago

Closed 9 years ago

#12461 closed defect (fixed)

[patch] repaint map after opening file

Reported by: kolesar Owned by: team
Priority: normal Milestone: 16.02
Component: Core Version: tested
Keywords: Cc:

Description

What steps will reproduce the problem?

  1. Create a new data layer.
  2. Open a GPX layer.
  3. Close GPX layer.
  4. Open it again.

What is the expected result?

Map shows GPX layer again.

What happens instead?

Nothing is shown. Data appears only on first zoom/pan.

Please provide any additional information below. Attach a screenshot if possible.

There is no explicit repaint after file opening. Map view is adjusted to file bounds that triggers repaint if view has changed, but if no change needed, there is no repaint after opening.

Attachments (2)

RepaintMapAfterFileOpen.patch​ (588 bytes ) - added by kolesar 9 years ago.
RepaintMapAfterFileOpen.fix.patch​​ (650 bytes ) - added by kolesar 9 years ago.

Download all attachments as: .zip

Change History (6)

by kolesar, 9 years ago

Attachment: RepaintMapAfterFileOpen.patch​ added

comment:1 by bastiK, 9 years ago

Resolution: → fixed
Status: new → closed

In 9688/josm:

applied #12461 - repaint map after opening file (patch by kolesar)

comment:2 by Klumbumbus, 9 years ago

Milestone: → 16.02

comment:3 by kolesar, 9 years ago

Resolution: fixed
Status: closed → reopened

Main.map can be null when multiple layers are loaded from session after fresh start of JOSM. This causes NPE. Attached fix.

by kolesar, 9 years ago

Attachment: RepaintMapAfterFileOpen.fix.patch​​ added

comment:4 by bastiK, 9 years ago

Resolution: → fixed
Status: reopened → closed

In 9707/josm:

applied #12461 - fix NPE for session load (patch by kolesar)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
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 .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.