[Geoprisma-dev] mapfishlayertree and initialview

[Yves Moisan]

Hi All,

I have found that layers that comprise a resource with an initialview
attached will be automatically activated upon loading the map with the
initialview *without* the mapfishlayer tree corresponding layer being
ticked on.  It is similar to the selfActivate option of the shortcut
widget, only the layer isn't ticked on in the tree.  

Another issue I found is that when the resource that has an initialview
widget attached to is part of a "compound WMS" layer, e.g.

<layer>
    <resourcenames>
        <resourcename>RSMunicipalities</resourcename>
        <resourcename>RSvegetation_tline</resourcename>
	<resourcename>RSstructures_mine</resourcename>
        <resourcename>RSstructures_tline</resourcename>
	<resourcename>RSroads_tline</resourcename>
        <resourcename>RSwater_river_tline</resourcename>
	<resourcename>RSwater_stream_tline</resourcename>
  <!--resourcename>RSmonitoring_stations</resourcename-->
        <resourcename>RSwater_monitoring_stations</resourcename>
    </resourcenames>
    <servicetype>wms</servicetype>
    <options>
        <layername>LYR_WMS</layername>
        <isbaselayer>false</isbaselayer>
        <projection>EPSG:32644</projection>
        <format>image/png</format>
        <transparent>true</transparent>
        <singletile>true</singletile>
    </options>
</layer>

Then all those layers will be shown on map load (without any of the
layers in the tree ticked on).  That is understandable, since there is
one call to MapServer, but that's not what we want on initialview.  In
the example above, the <!--resourcename> tag is the one with the
initialview.  I had to take it out of the compound WMS layer and shove
it into a layer of its own, so that means any layer we want an
initialview on cannot be used in an optimized compound WMS layer.
Should I file a bug for that ?  And should I file a bug for the
layertree not being ticked on or is it me ?

Cheers,

Yves