On Mon, 28 Mar 2005 12:00:02 -0500, Joe Berkovitz <[EMAIL PROTECTED]> wrote:
> But it's still not as good as I would like, because Images are merely > clip holders, not the actual image clips themselves. Each time one sets > the "source" attribute, a brand new MovieClip object for the image is > created via loadMovie() (which clip in turn becomes the 'contentHolder' > property of the Image). So the other option is to just hide and show the image objects. You could maintain a map of image URLs to their corresponding objects. If there's one already in the map, you simply set its _visible to true. If there isn't one, you create one and add it to the map. This would be memory-intensive and not advisable for something that has a large number of images. But say if you have a fixed number of images and they keep swapping in and out, you can do the math for how much memory you'd need to keep them all loaded at once. > Incidentally, the map demo doesn't seem to make use of the browser > cache. I haven't checked, but this might be true. I know that Google sets an Expires header of something like January 2006, but maybe it gets stripped off along the way (the GIF->JPEG conversion proxy). As an aside, check this out: http://www.xamlon.com/flash/demos/mapserver/ They're caching images on the server. http://www.xamlon.com/flash/demos/mapserver/maps/map-4--3-11.jpeg Unless you unselect the cache option, in which case they get fetch fresh images. http://www.xamlon.com/flash/demos/mapserver/map.aspx?x=4&y=-3&z=11 Manish Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
