Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: Missed (?) dependency reference to a Ext.util.Point in Ext.EventObjectImpl

    You found a bug! We've classified it as EXTJS-9956 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #11
    Sencha Premium User evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    19,255

    Default

    Maybe I'm missing something then:

    http://screencast.com/t/o6dgtHmPYJjI

    I changed the include to grab the debug as you suggested. I load up the example. There's no exceptions. Using a clean 883 download.
    Twitter - @evantrimboli
    Former Sencha framework engineer, available for consulting.
    As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

  2. #12
    Sencha Premium Member
    Join Date
    Apr 2010
    Location
    Wellington, New Zealand
    Posts
    123

    Default

    Are you sure the ext-debug version was loaded? It's not possible that it works for you.

  3. #13
    Sencha Premium Member
    Join Date
    Apr 2010
    Location
    Wellington, New Zealand
    Posts
    123

    Default

    http://screencast.com/t/nk6XTpkw - here is a video with an exception

  4. #14

    Default

    Here is some sample code to reproduce the issue. I have tested on 4.2.1.883
    You can see the error when you try reordering the nodes in the tree.

    Code:
    <html><head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
        
        <link rel="stylesheet" type="text/css" href="../../resources/ext-theme-classic/ext-theme-classic-all-debug.css" />
        <script type="text/javascript" src="../../ext-debug.js"></script>
    
    
        <script type="text/javascript">
    
    
            Ext.require('Ext.tree.*');
            Ext.require('Ext.data.*');
    
    
            Ext.onReady(function(){
                
                Ext.create('Ext.tree.Panel', {
                    height: 400,
                    width: 350,
                    renderTo:'tree',
                    store: new Ext.data.TreeStore({
                        root: {
                            expanded: true,
                            text: "My Root",
                            children: [
                                { text: "Child 1", leaf: true },
                                { text: "Child 2", expanded: true, children: [
                                    { text: "GrandChild", leaf: true }
                                ] }
                            ]
                        }
                    }),
                    viewConfig: {
                        plugins: {
                            ptype: 'treeviewdragdrop'
                        }
                    }
                });
            });
    
    
        </script>
        
    </head>
    <body>
        <div id="tree"></div>
    </body>
    </html>
    Uncaught TypeError: undefined is not a function ext-debug.js:12187
    Ext.define.getPoint ext-debug.js:12187
    Ext.define.handleMouseDown DragDrop.js:812
    Base.implement.callParent ext-debug.js:4266
    Ext.define.handleMouseDown DragSource.js:343
    Ext.define.onItemMouseDown DragZone.js:89
    fire ext-debug.js:9818
    continueFireEvent ext-debug.js:11210
    fireEventArgs ext-debug.js:11188
    fireEvent ext-debug.js:11174
    Ext.define.processUIEvent View.js:582
    Base.implement.callParent ext-debug.js:4266
    Ext.define.processUIEvent View.js:258
    Ext.define.handleEvent View.js:509
    (anonymous function)
    wrap ext-debug.js:10566

  5. #15
    Sencha Premium User evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    19,255

    Default

    Looks like I was getting a weird caching issue. As it goes, when the ext-debug file gets built it strips out the dependency loading which is incorrect. So it's not really a framework bug, but one in Cmd. Anyway, we'll look into it, sorry for the confusion.
    Twitter - @evantrimboli
    Former Sencha framework engineer, available for consulting.
    As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

  6. #16
    Sencha User mschwartz's Avatar
    Join Date
    Nov 2008
    Location
    San Diego, Peoples' Republic of California
    Posts
    2,061

    Default

    I ran into this today.

    A fix, since nobody's really posted one (I think) is:

    Code:
    requires: [
       ...
       'Ext.util.Point'
    ]
    I don't get the exception with that in my code.

  7. #17
    Sencha Premium User
    Join Date
    Nov 2010
    Location
    Chicago
    Posts
    2,425

    Default

    Quote Originally Posted by mschwartz View Post
    I ran into this today.

    A fix, since nobody's really posted one (I think) is:

    Code:
    requires: [
       ...
       'Ext.util.Point'
    ]
    I don't get the exception with that in my code.
    Already posted by zerkms:

    "Yep, and the trivial fix would be to replace `uses` to `requires` in the declaration"

  8. #18
    Sencha User mschwartz's Avatar
    Join Date
    Nov 2008
    Location
    San Diego, Peoples' Republic of California
    Posts
    2,061

    Default

    Actually the fix was in your own post, not his. He explained the issue, but didn't present any solution as code that might help people resolve it.

    Thanks to the forums for helping resolve these kinds of things when they (rarely) arise!

  9. #19
    Sencha Premium User
    Join Date
    Nov 2010
    Location
    Chicago
    Posts
    2,425

    Default

    I believe the difference between uses and requires is only in development since in production all code is already loaded. So making this change should have no impact on production code.

  10. #20
    Touch Premium Member
    Join Date
    Jun 2008
    Location
    Germany, Dortmund
    Posts
    249

    Default

    Any news on this?

    The bug is still represent in

    ext-4.2.2.1162

    I am using Sencha Architect and the workaround using
    requires Ext.util.Point
    fixes it, but that should not be the final solution ;-)

    Cheers Holger

Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

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