Garthan wrote: > The ability to show relationships in kml with a nested tree like > structure is one significant benefit kml has over other GeoXml data > structures. Hence the ability to show those structures in a > understandable way in an API page (similar to the side bar of > maps.google.com) has been one of the features of my GeoXml parser > since it first diverged from egeoxml. > > An issue which caused multiple sub folders when nested in kml to > sometimes draw over one another in the side bar it is now fixed and > kml can now be freely structured with folders set to all open or be > opened with the tag <open>1</open> in the kml and it will render > correctly. It occurs some might not know what I am talking about...
http://www.dyasdesigns.com/geoxml --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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?hl=en -~----------~----~----~----~------~----~------~--~---
