Hi Seth, hi Marc,

I guess Seth means the difference between v2.0.x and v2.1. To get the
compatibility with ExtJS 5 we had to rewrite some parts of tree
structure. One thing was to introduce a util-class which handles
visibility of the layers according to the treenode's checked state (as
Seth described).
What I don't understand is the thing that  all "param-layers" turn off
whenever any of the nodes are unchecked. In the
'updateLayerVisibilityByNode' we just work on the selected node and its
dependent layer. It should not be the case that
other layers (besides base layers) are affected. As Marc already wrote:
Is there any code we can see?

As short-term-solution you can either overwrite the
'updateLayerVisibilityByNode' function or you unbind it and bind your
own 'checkchange'-handler.

Cheers
Chris

--
Christian Mayer
GIS-Spezialist & Software-Developer

meggsimum
Hauptstraße 165a  | 67125 Dannstadt-Schauernheim
i...@meggsimum.de | www.meggsimum.de

Am 03.09.2015 um 17:02 schrieb Marc Jansen:
> Hi Seth,
>
> when you say 'previously', what version are your refering to?
>
> Is there code one can see for your approach towards 'parameter nodes'?
>
> Thanks for the feedback!
>
> Best,
> Marc
>
> On 03/09/15 12:29, geographika wrote:
>> Hi devs,
>>
>> I have been testing the 2.1 version with my codebase and have run
>> into a few issues with the new approach to layer visibility and node
>> synching in the GeoExt.tree.Panel
>> Previously updateLayerVisibilityByNode was handled by the different
>> node plugins. In 2.1 it is moved into the GeoExt.tree.Util class, and
>> applied to "checkchange" events for all nodes in the tree.
>>
>> See:
>>
>> https://github.com/geoext/geoext2/blob/master/src/GeoExt/tree/Panel.js
>> https://github.com/geoext/geoext2/blob/master/src/GeoExt/tree/Util.js
>>
>> However this means other custom layer types, such as parameter nodes
>> (that I'm trying to implement as a pull request), turn off whenever
>> any of the nodes are unchecked.
>> There doesn't seem to be an easy way to override this (apart from
>> removing the event from the whole tree).
>> The updateLayerVisibilityByNode takes into account "isBaseLayer", but
>> maybe some other property could be added to allow skipping or
>> overriding these checks?
>> Or is there another way?
>>
>> Good luck with the upcoming release!
>>
>> Regards,
>>
>> Seth
>>
>> --
>> web:http://geographika.co.uk
>> twitter: @geographika
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@geoext.org
>> http://www.geoext.org/cgi-bin/mailman/listinfo/dev
>
>
> -- 
>
>   Dipl.-Geogr. Marc Jansen
>   — Anwendungsentwickler —
>
>   terrestris GmbH & Co. KG
>   Pützchens Chaussee 56
>   53227 Bonn
>
>   Tel:   +49 (0)228 / 96 28 99 -53
>   Fax:   +49 (0)228 / 96 28 99 -57
>
>   Email: jan...@terrestris.de
>   Web:   http://www.terrestris.de
>
>   Amtsgericht Bonn, HRA 6835, Komplementärin: terrestris Verwaltungs-
>   gesellschaft mbH, vertreten durch: Hinrich Paulsen, Till Adams
>
>
> _______________________________________________
> Dev mailing list
> Dev@geoext.org
> http://www.geoext.org/cgi-bin/mailman/listinfo/dev

_______________________________________________
Dev mailing list
Dev@geoext.org
http://www.geoext.org/cgi-bin/mailman/listinfo/dev

Reply via email to