Roald,
there are some constructs that rely on layer names being keys in
MapPaneOL.oLlayers, like the following snippet from
lib/widget/OverviewMap.js
if (objRef.layerNames) {
for (var i = 0; i < objRef.layerNames.length; i++) {
for (var j in map.mbMapPane.oLlayers) {
Hi,
On Nov 22, 2007 1:49 PM, Roald de Wit (Sourceforge)
<[EMAIL PROTECTED]> wrote:
> However, just looking at what you wrote below would tell me that I have
> been slack in changing the reference to layerId where you see layerName in
> moveLayerDown. That surprises me since I put some effort into
Hi Andreas,
I will be away from work and Internet till Tuesday (moving house). Thanks
a lot for looking into the code.
However, just looking at what you wrote below would tell me that I have
been slack in changing the reference to layerId where you see layerName in
moveLayerDown. That surprises m
Hi Jorge,
welcome to the Mapbuilder community!
On Nov 22, 2007 12:35 PM, <[EMAIL PROTECTED]> wrote:
> When a feature is inserted all the layers are refreshed. There is some way
> of avoiding the refreshment of the not modified layers?
Currently, you cannot. But in the SVN trunk version of Mapbu
Hy,
My name is Juez, Jorge. I'm from Spain/Europe. I´m starter in MapBuilder.
When a feature is inserted all the layers are refreshed. There is some way
of avoiding the refreshment of the not modified layers?
Thanks
La información contenida en este mensaje de correo electrónico es confidencial.
Cameron,
The solution as done now with only works for 1 layer and is
intended to have an easy way to have a single google layer in 1.5. We
will need to modify the code to handle multiple baselayer-types in a
context doc and allow for switching baselayers. We can discuss OWS
context as well in
Hi all,
> -MapPaneOL.prototype.getLayer = function(objRef,layerName) {
> - return objRef.model.map.getLayer(objRef.oLlayers[layerName].id);
> +MapPaneOL.prototype.getLayer = function(objRef,layerId) {
> + if(objRef.oLlayers[layerId] && objRef.oLlayers[layerId].id) {
> +return objRef.model.ma
Hi Roald,
so you really want to have that baby in the 1.5 release. Here is a
detailled review.
lib/model/Context.js
The layer id was only introduced for OWSContext, not for Web Map
Context. So maybe Context.js should not be touched. If you revert
Context.js, and all examples still work, I would s
