Opened 14 years ago
Closed 13 years ago
#463 closed defect (fixed)
Multi-map support broken in trunk
| Reported by: | jng | Owned by: | madair |
|---|---|---|---|
| Priority: | P2 | Milestone: | Future |
| Component: | Widgets | Version: | SVN |
| Severity: | Major | Keywords: | |
| Cc: | Browser: | All | |
| External ID: | Operating System: | All | |
| state: | New |
Description
The 2.2 branch of fusion has basic support for multiple maps in a MapGroup (#428)
Unfortunately, changes in the trunk has broken this support. The legend widget now only renders the layers of the first map in the MapGroup, where previously (in the 2.2 branch) it will properly handle all the maps in the MapGroup.
Attachments (4)
Change History (6)
by , 14 years ago
| Attachment: | multimap.PNG added |
|---|
by , 14 years ago
| Attachment: | 463_attempt.patch added |
|---|
1st attempt to fix the multi-map suport in the Legend widget
comment:1 by , 14 years ago
Ok, I noticed that the renderLegend() in LegendRendererDefault looks very similar to what was commented out here.
http://trac.osgeo.org/fusion/browser/branches/fusion-2.2/widgets/Legend.js
So I tried porting over the renderLegend() logic present in the 2.2 version and got very close (see attached multimap.png). I must be missing something. Attached is a patch of what I did to get the produced screenshot (463_attempt.patch)
Notice however that only the first map is being rendered (due to OpenLayers being updated for #464). This is better than what we had before (nothing), but something is still obviously broke.
by , 14 years ago
| Attachment: | multimap_working.PNG added |
|---|
Screenshot of the same appdef under our github fork for comparison
comment:2 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Multi-map support is working again
Screenshot of attempted patch (almost there)