That would be ideal... although a back door should be available in case 
Google Maps API gets changed radically.

David

John Callahan wrote:
> Actually, could we just include the GM API version (along with the API 
> key) in the map-extension.js call?  It'd be very easy to parse that 
> parameter and provide benefit in many cases.  Something like the 
> following (the default would be simply gmapi=2)
>
> <script 
> src="http://api.simile-widgets.org/exhibit/2.2.0/extensions/map/map-extension.js?gmapi=2.94&gmapkey=...key...";
>  type="text/javascript"></script>
>
> - John
>
>
>
> David Huynh wrote:
>   
>> I believe that if you don't specify any map key when including the map 
>> extension, but including gmap yourself before, then the map extension 
>> won't try to load gmap.
>>
>> Look in
>>     
>> http://api.simile-widgets.org/exhibit/2.2.0/extensions/map/map-extension.js
>> You can see there's a check
>>     !("GMap2" in window)
>>
>> David
>>
>> John Callahan wrote:
>>   
>>     
>>> I see the same problem.  For me, the error appeared when displaying the 
>>> map view once, then displaying another view (like table, timeline, 
>>> tile), then going back to the map view.  I didn't perform any filtering 
>>> and the error still appeared.
>>>
>>> This is probably a versioning issue with Google Maps API.   I changed 
>>> the GM API version in map-extension,js (lines 37 - 41) from v=2 to 
>>> v=2.94 and the error disappeared.  I run Exhibit locally and it was easy 
>>> for me to make this change; not so easy if you use api.simile-widgets.org.
>>>
>>> I only chose 2.94 because I used that version is an app I built about a 
>>> year ago and it was the first one that popped into my mind!  Of course, 
>>> I would go with the latest version that keep everything working (until 
>>> the true cause is found out and fixed.)
>>>
>>>
>>> For details on the GM API version number scheme, see 
>>> http://groups.google.com/group/Google-Maps-API/web/javascript-maps-api-versioning
>>>
>>> - John
>>>
>>> **************************************************
>>> John Callahan
>>> Geospatial Application Developer
>>> Delaware Geological Survey, University of Delaware
>>> 227 Academy St, Newark DE 19716-7501
>>> Tel: (302) 831-3584  
>>> Email: [email protected]
>>> http://www.dgs.udel.edu
>>> **************************************************
>>>
>>>
>>>
>>>
>>> mmauri wrote:
>>>   
>>>     
>>>       
>>>> Hi everybody.
>>>> In a html page I defined three views (map, tabular, tile). In the map
>>>> view I set true the property ex:overviewControl.
>>>> I found out that filtering the results in the tabular or tile views
>>>> and then selecting the map view, the  filtered results cannot be
>>>> plotted due to some errors. You can try by yourself using the
>>>> president example and adding the property ex:overviewControl into the
>>>> map div section.
>>>> This problem disappears changing ex:overviewControl to false.
>>>>
>>>> HTH
>>>> Marco
>>>>     
>>>>   
>>>>     
>>>>       
>>>>         
>>>   
>>>     
>>>       
>>     
>>   
>>     
>
> >
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" 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/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to