Flexuous

I came across this strange behavior  in ExtJS 3.2 on Firefox (haven’t tested in other browsers) If you name the element of an object the same as the object you are inserting it absorbs this object instead of nesting it.  For example….

//In ExtJS.... The getAt method on a dataStore returns an object such that record.data exists
var record = myDataStore.getAt(1);   

//If I then pass that to a constructor of another object such as a custom window
var win = new myWindow({
                record:record,
                width:500
              });

// Where myWindow's constructor is defined to take an argument object of config like so...
Window = Ext.extend(BCC.trace.TraceWindow,{
         constructor: function(config){ .... }
         .....
})

I would expect that you would have an object like inside the constructor.

       config.record.data

but instead you get

       config.data

Oddly enough… .if you  call it  like this instead

var rec= myDataStore.getAt(1);   

var win = new myWindow({
                record:rec,
                width:500
              });

You get the correct

       config.record.data

Why does it do this??? I have no idea. Seems sort of strange to me but perhaps it is supposed to work this way.

There are a couple of syntaxs for extending a ‘class’ with the Ext library. I prefer the following syntax.

MyNewForm = Ext.extend(Ext.form.FormPanel,{

constructor:function(config){
…..
MyNewForm.superclass.constructor.call(this,config);
….
},

newMethod:function(){
}
})

I had a strange problem today. I had two almost identical classes. In one I could get a console log statement in the constructor to output. In the other I could not get it to work. The problem was I also didn’t get an error. The problem component would initialize and I could see it in the firebug dom tree.

Took me about 20 minutes to figure out the problem. Turns out I typed ‘construtor’ on the second class. Since Ext automatically calls the parent class constructor (if you do not override) I wasn’t getting an error.

Crazy how little typos can waste a lot of time…. so if you have this same problem, make sure you actually typed what you though you typed.