Just because I love seeing how innovative people get with this GIS implementations, if your application is in the public domain could you send me the URL? I would love to see it in action/play with it. Thanks, Alessandro Ferrucci
On Thu, Mar 8, 2012 at 12:23 PM, artisan <[email protected]> wrote: > > > On Friday, January 6, 2012 4:01:30 PM UTC-7, Alessandro Ferrucci wrote: >> >> Google's Flash API is going away so regardless of a work-around your best >> bet if you want your engine to survive longer than Google's promised life >> span of a defunct technology is to port your engine to something like Open >> Scales. >> >> On Fri, Jan 6, 2012 at 3:51 PM, artisan <[email protected]> wrote: >> >>> Hi, >>> I guess my first post was eaten, to repeat: I've built a dynamic >>> multi-map engine that uses an advanced datagrid to display data that >>> changes across time and modelling technique. The engine can display up to >>> 24 maps without using Google's technology. When I include that technology, >>> however, and start dynamically building (and destroying) multiple map >>> instances, the GC does not keep up - memory keeps getting allocated until >>> the browser fails. My solution has been to create a single (hidden) map >>> instance and supply it with the appropriate overlay imagery as the >>> datagrid's item renderer iterates across cells. Unfortunately when I use >>> bitmapdata.draw(map) to capture the map as an image and place it in the >>> appropriate cell, the datagrid displays nothing if I run the application >>> over the Internet (locally, it works). Digging into these forums, it looks >>> like I'm violating Google's TOS, which would explain the empty datagrid. >>> Does anyone have a work-around? Otherwise I'm going to have to scrub every >>> last byte of Google's technology out of my engine. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google Maps API For Flash" group. >>> To view this discussion on the web visit https://groups.google.com/d/** >>> msg/google-maps-api-for-flash/**-/36b5_FuaX1EJ<https://groups.google.com/d/msg/google-maps-api-for-flash/-/36b5_FuaX1EJ> >>> . >>> To post to this group, send email to google-maps-api-for-flash@** >>> googlegroups.com <[email protected]>. >>> To unsubscribe from this group, send email to google-maps-api-for-flash+ >>> **[email protected]<google-maps-api-for-flash%[email protected]> >>> . >>> For more options, visit this group at http://groups.google.com/** >>> group/google-maps-api-for-**flash?hl=en<http://groups.google.com/group/google-maps-api-for-flash?hl=en> >>> . >>> >> >> >> >> -- >> Signed, >> Alessandro Ferrucci >> > > > > Alessandro, > Thanks! Your advice made all of the difference in the > world. I now have a functioning, dynamic multi-map engine. Where Google > failed, Openscales worked like a champ. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps API For Flash" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-maps-api-for-flash/-/FLlnxq2gfUMJ. > 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. > -- Signed, Alessandro Ferrucci -- 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.
