Results 1 to 2 of 2

Thread: Ext.Map - maprender event's 2nd argument is always null

Hybrid View

Previous Post Previous Post   Next Post Next Post
    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User mystix's Avatar
    Join Date
    Mar 2007

    Exclamation Ext.Map - maprender event's 2nd argument is always null

    Original bug report from (marked fixed, but still broken in Touch 2.2.1).

    Ext.Map's maprender event always returns null as the 2nd argument because a direct reference to the private map variable is used.

    Ext.Map#onTilesLoaded needs to use a proper getter instead:
    Ext.define('Ext.bugfix.Map', {
        override: 'Ext.Map',
        onTilesLoaded: function() {
            // this.fireEvent('maprender', this,; // wrong
            this.fireEvent('maprender', this, this.getMap()); // right
    Tested on Touch 2.2.1.

  2. #2
    Sencha - Support Team
    Join Date
    Oct 2011


    Thanks for bringing this our attention. I see that this has already been fixed in Touch 2.3.0.
    Get more personalized support via a support subscription.

    Need more help with your app? Hire Sencha Services [email protected]

    When posting code, please use BBCode's CODE tags.

    Need to include a test case use:
    The official Sencha Fiddle

Posting Permissions

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