Hi Daniel,

That's really helpful - thank you. Our next release does have the check and 
timeout you suggest, so if we're really luckt that will sort it out.

In terms of how we're using maps. aside from the JS API load (which I 
showed above), I just construct the maps object in the widget initialise 
method like the charts above.

            this.googlemap = new 
google.maps.Map(this.element.children("div")[0], options);

Interestingly, we are not getting any reports of the maps not working 
properly; but then we do have a Premium Plan for the Maps APIs, hence my 
original question over whether the charts were being throttled at your 
end...

The only thought I;ve and is whether there is any chance the TypeScript 
packages might be interfering?

*google.visualization.d.ts:*
// Type definitions for Google Visualisation Apis
// Project: https://developers.google.com/chart/
// Definitions by: Dan Ludwig <https://github.com/danludwig>, Gregory Moore 
<https://github.com/gmoore-sjcorg>
// Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped

declare namespace google {
    function load(visualization: string, version: string, packages: any): 
void;
    function setOnLoadCallback(handler: Function): void;
    function setOnLoadCallback(handler: () => void): void;

    // https://developers.google.com/chart/interactive/docs/basic_load_libs
    namespace charts {
        function load(version: string, packages: Object): void;
       // ...etc
    }

    //https://developers.google.com/chart/interactive/docs/reference
    namespace visualization {
    }

   // .. etc
}


*google.maps.d.ts:*
// Type definitions for Google Maps JavaScript API 3.25
// Project: https://developers.google.com/maps/
// Definitions by: Folia A/S <http://www.folia.dk>, Chris Wrench 
<https://github.com/cgwrench>, Kiarash Ghiaseddin 
<https://github.com/Silver-Connection/DefinitelyTyped>
// Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped

declare namespace google.maps {
  export class Map extends MVCObject {
     constructor(mapDiv: Element, opts?: MapOptions);
     fitBounds(bounds: LatLngBounds): void;
     // ... etc
  }
}

I'm not sure if these files get baked into the app - I had thought that 
they were just compile time support files?

I'm hoping to get access to the debugger network tab of a cusomter 
experincing the problem today, and if I do then I'll post the results.

Many thanks again for all your help.

James

-- 
You received this message because you are subscribed to the Google Groups 
"Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/44cf9bbb-c2a2-46c8-a9dd-1a276140646f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to