Setting opacity on a parent and allowing the opacity to inherit.. seems like a more efficient way. you have the dom object of the images... would getting the first and tracing back up work?
On May 28, 10:39 am, Marcelo <[email protected]> wrote: > Garthan, > > Yes, I know it doesn't work on my Nexus One either, but that's only > because of the slider. I'll see to modify the slider sometime. > > As for the array, it is not needed. You could just create the IMG and > return it. I was just trying to create fewer DOM IMG objects by > reusing existing ones. The API doesn't seem to do that because if you > zoom in and out again it calls the getTile() function again for the > same tiles, which is good if you need to refresh the tiles > dynamically. > > -- > Marcelo -http://maps.forum.nu > -- > > On May 28, 4:45 pm, Garthan <[email protected]> wrote: > > > Looking under the hood... you are tracking up to a hundred tiles > > arbitrarily... removing the earliest ones in the array > > and removing and re-adding them if they dont exist... sigh > > > This is somehow better than making getOpacity an over-rideable > > function call? > > I find my v2 ...love increasing by the moment ;-p > > > Over all this is going to take some adjustments. -- 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.
