It's more in the rebuild process. Basically it makes the compiler unworkable, each time it rebuilds it seems to want to delete, then recopy all the files into the debug folder. Performance of the running program is great!
I guess the solution is to write the program without the overlay (or at least just the lower zoom levels), then add the higher zoom levels when I am ready to make my final build. cheers On Jan 29, 2:47 pm, pamela fox <[email protected]> wrote: > Hi Lynxmap- > > Only the tiles for the current viewport should be loaded into the map > at one time - Flash shouldn't ever encounter 300,000 tiles. Why is it > doing so? > > - pamela > > On Thu, Jan 29, 2009 at 2:41 PM, [email protected] <[email protected]> wrote: > > > This is more of a Flex issue than a Google API. > > > Trying to get a countywide overlay tile set to perform with Flex has > > been quite challenging. For Zoom 18, I originally had over 300,000 > > tiles. The tile set is a transparent PNG overlay of parcel > > boundaries, so over 70% of these were blank. I was able to delete all > > the blank ones by examining their file size (a 256x256 png file with > > nothing in it takes 172 bytes, apparently). Next I used PNG OUT to > > optimize the tiles, saving another 30% in size. So far, so good, all > > seems well. > > > The real issue, though it just the quantity of files--Flex has a hard > > time building and rebuilding them. Any ideas on how to isolate a > > large quantity of files from the normal build process in Flex? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" 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-api-for-flash?hl=en -~----------~----~----~----~------~----~------~--~---
