Results 1 to 4 of 4

Thread: Google Map RC2, useCurrentLocation

    Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. #1
    Sencha User
    Join Date
    Oct 2011
    Posts
    20
    Vote Rating
    0
      0  

    Default Google Map RC2, useCurrentLocation

    Hello,
    it seems like the Ext.Map component doesn't get initialized correctly when it is configured for using the current location - with RC1 it worked as expected.

    For example:
    Code:
                var mapPanel = new Ext.create("Ext.Panel",{
                    fullscreen: true,
                    layout:'fit',
                    id: 'myPanel',
                    items: [{
                                    xtype: 'map',
                                    id :'map',
                                    useCurrentLocation: true,
                    }]
                });
    Will not create a map.
    Code:
    mapPanel.down("map").getMap() == null
    Whereas:
    Code:
                var mapPanel = new Ext.Panel({
                    fullscreen: true,
                    layout:'fit',
                    id: 'myPanel',
                    items: [{
                          xtype: 'map',
                        id :'map',
                        useCurrentLocation: false,
                    }]                
                });
    works like a charm.

    My browser supports geo location.

    Can anybody confirm this issue?

    Thanks,
    Seb.

  2. #2
    Sencha User Jamie Avins's Avatar
    Join Date
    Mar 2007
    Location
    Redwood City, California
    Posts
    3,661
    Vote Rating
    19
      0  

    Default

    There were several issues in PR2 (this is one of them) with Map that should be fixed in the next release.

    Sencha Inc

    Jamie Avins

    @jamieavins

  3. #3
    Sencha User
    Join Date
    Mar 2012
    Posts
    4
    Vote Rating
    0
      0  

    Default

    I can verify that this is still broken on RC. Current workaround is to set useCurrentLocation: false in config, but this.setCurrentLocation(true) in initialize.

  4. #4
    Sencha User
    Join Date
    Jul 2012
    Posts
    15
    Vote Rating
    0
      0  

    Default Thank you

    Thank you for sharing this tip! This bug/problem STILL exists in 2.1.1 anytime you manually create a map instead of declaring it in an xtype/config. Since you have to get the maprender event to fire before you can actually do anything with google (you need the Ext.Map.getMap() wrapped google map), you HAVE to create the map in a container config - which means you have to display it.

    Similarly, if you DO declare a map in a config and set it hidden, the maprender event will never fire and this getMap() will return null. It seems that if you want to use Ext.Map you're meant to actually display the map to user, as opposed to merely using it behind the scenes to populate lists or something similar. Granted, you could just do all your Google map operations by writing your own javascript, but it seems silly given there's a perfectly good wrapper Sencha has provided. Hopefully this is considered in a future release
    Last edited by hawkinbj; 7 Mar 2013 at 5:08 PM. Reason: add 2.1.1

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •