Tim McGee

thinking out loud: using `aspect.after` and `aspect.around` isn't "changing the api" as I interpreted it when reading earlier. So I could be supportive of this approach. Still need to give...

Yep. Whatever we do needs to also correctly handle other scenarios such as: 1. a group layer id is included in the layer's `imageParameters` like we have in the [demo](https://github.com/cmv/cmv-app/blob/develop/viewer/js/config/viewer.js#L186-L189):...

Continued thought. # 2 above: ``` javascript layerControlLayerInfos: { layerIds: [0, 2, 4, 5, 8, 9, 10, 12, 21] } ``` may provide the correct results. More investigation is needed...

I am completing a redesign of how group layers within a Dynamic layer are handled within the layerControl. The behavior will be similar to the newly introduced "Group Layer". More...

No, currently toggling the layer visibility would not change the visibility of the sub layers. This is intentional as I think that would be undesirable for many (most?) implementations. There...

Regarding your edit: The behavior is consistent with what is implemented for the Grouped layer currently and how most 3-state check boxes work on the web (so hopefully familiar to...

I am hoping to avoid that as much as possible but perhaps may not succeed in all cases. What cannot or should not be changed by republishing can hopefully be...

@mayur9785 Looks like a lot of interesting work. It would be much easier to visualize this (and possibly contribute) if you provided a working example with demo in a github...

Hi @mayur9785 please add all the individual files in the repo instead of a single rar file. That would greatly help myself and others that may want to contribute. :)...

@mayur9785 Thanks for reporting. Confirmed in the demo. In my testing, the Identify worked but the InfoWindow doesn't display. Maybe there is a conflict recently introduced within the Esri Editor...