Image layers from previous sessions are sometimes loaded in wrong order
Bug #357217 reported by
Keith Hughitt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Helioviewer.org |
Fix Released
|
Low
|
Keith Hughitt | ||
Bug Description
When loading a view from cookies, sometimes the first layer in the layer manager may be associated with the front or "top" layer instead of the bottom layer.
| Changed in helioviewer.org: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
Revision history for this message
| Keith Hughitt (keith-hughitt) wrote | #1 |
| Changed in helioviewer.org: | |
| milestone: | none → 2.0.1 |
| assignee: | nobody → Keith Hughitt (keith-hughitt) |
| status: | Confirmed → Fix Committed |
| Changed in helioviewer.org: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This relates to the asynchronous nature of the queries. All of the layers are queried simultaneously, and they are then added to the tileLayerManager in the order that the responses are recived, which is not guaranteed to match the order that the requests were sent.
The ideal approach to resolving this would be to add functionality to the TileLayerAccordion to support manual specification of placement, instead of always placing new layers at the end.