-
4 Apr 2013 1:39 AM #1
maprender event's 2nd argument is undefined
maprender event's 2nd argument is undefined
Just downloaded to test ST 2.2.0-rc.
Using Ext.Map, the maprender(comp, gmap) event has two arguments, the first being the map component, and the second being the google map.
The console log says: undefined. Using it with ST 2.1.1 it prints the google map object.Code:maprender: function(comp, gmap) { console.log(gmap); }
-
4 Apr 2013 6:02 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,710
- Vote Rating
- 436
Thanks for the report! I have opened a bug in our bug tracker.
-
23 Apr 2013 6:44 AM #3
NOT fixed
NOT fixed
This one slipped through the cracks of your RC -- Still broken.
Ext.Map
Code:// @private onTilesLoaded: function() { this.fireEvent('maprender', this, this.map); //< --- use getter this.getMap() or this._map },/**
* @author Chris Scott
* @business www.transistorsoft.com
* @rate $120USD / hr; training $500USD / day / developer (5 dev min)
*
* @SenchaDevs http://senchadevs.com/developers/transistor-software
* @twitter http://twitter.com/#!/christocracy
* @github https://github.com/christocracy
*/
-
23 Apr 2013 11:21 AM #4
I reported it for 2.2.0-RC. The download is still the same, so no new RC provided since. The "Fixed" might be an indication that it will be included in the release following 2.2.0-RC.
-
26 Apr 2013 3:25 AM #5
map doesn't load in final release when
useCurrentLocation = true is added. Is there some kind of temporary workaround for it?
-
26 Apr 2013 6:42 AM #6
My Mistake. I needed to do a reboot of my device (Galaxy S3). Everything working now
-
10 May 2013 8:01 AM #7
This was still an issue for me on both iOS and Android after upgrading to Sencha Touch 2.2. The Google map component was undefined. Here's the patch that I applied to fix it. I simply assigned the map via the getter to the gMapComponent. This worked for both iOS and Android.
Code:listeners: { maprender: function(extMapComponent, googleMapComp) { googleMapComp = extMapComponent.getMap(); var theView = Ext.ComponentQuery.query('retailerMap')[0]; var lat = theView.config.data.retailer_latitude; var lng = theView.config.data.retailer_longitude; extMapComponent.setMapCenter({latitude: lat, longitude: lng}); var marker = new google.maps.Marker({ position: position = new google.maps.LatLng (lat,lng), map: googleMapComp, }); } }
Success! Looks like we've fixed this one. According to our records the fix was applied for
TOUCH-4269
in
a recent build.


Reply With Quote