Opened 14 years ago
Closed 14 years ago
#426 closed defect (fixed)
fix the aMaps[0] TODOs
Reported by: | madair | Owned by: | madair |
---|---|---|---|
Priority: | P1 | Milestone: | 2.2 |
Component: | Widgets | Version: | SVN |
Severity: | Major | Keywords: | |
Cc: | Browser: | All | |
External ID: | Operating System: | All | |
state: | New |
Description
Sprinkled throughout widget code are some TODOs to figure out how to deal with multiple maps in a MapGroup. Now that applications are using commercial baselayers we need to figure out how to fix these.
I am proposing that each <Map> in a <MapGroup> will have an optional 'id' attribute and widgets that depend on a specific <Map> can point to that ID in their extension. If there is only one <Map> then behaviour is as before and defaults to the aMaps[0] layer. This would be implemented through a new widget method called getMapLayer(layerId) where layerId is an optional argument.
changes applied in [2365]