On Jul 24, 10:56 pm, Kesuke <[email protected]> wrote: > > "IF layer X is shown, layer Y must also be shown" > "IF layer X is shown, layer Y must be hidden" > "IF layer X is shown, layer Z must be shown and Y must be hidden" etc. >
I was wondering if these display rules cascade, ie if show(X) triggers show(Y), then can show(Y) trigger other display rules? > > In V2 controlling the z-index and the rules was much easier, as > show(); and hide(); could be used and you could insert layers at a > specific z-index (a bit like the MCVarray, only the array is dynamic > so if a layer is removed the whole array moves down 1, messing up the > z-index order). yeah V2 sounds more logical, but V3 more efficient, so we need a data structure which reflects the relationships between all layers and their display state, backed by the V3 MVCArray, which only contains the visible layers in the correct order. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
