On Jul 29, 4:40 am, William <[email protected]> wrote:
> I imagine if you want to view layer B when layer A is visible,
> and if parts of B are above A and parts below A, then A needs
> to become two layers C and D, to be displayed in order C,B,D.
This controller idea sounds perfect, and your absolutely right about
the layer structure - in photoshop where the drawings were made the
layers are already in that sort of order (e.g. A can't be both above
and below B). I'll upload some more layers later that I can use to
demonstrate/test this practically.
These specific 'exceptions' only occur about 15 times so a few lines a
bit like this in the controller will probably do it nicely.
if( id(A).visible == true ){ id(B).visible = true};
if( id(C).visible == true ){ id(D).visible = false};
> this didn't work ... the ImageMapType isn't a MVCObject. So instead I
> made a new ImageMapType when there's a change in opacity. SQLArray
> now ensures the MVCArray is up to date by listening to changes in the
> "select" and "where" attributes of its MVCObjects.
This should work very nicely, and in addition to the opacity handler
opens up potential for other 'live' modifications.
I should have more tiles online by this weekend when I get some free
time, then I can test the idea with a more complex set of images.
--
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.
