1. #1
    Ext JS Premium Member
    Join Date
    Sep 2007
    Posts
    55
    Vote Rating
    0
    mvarshavsky is on a distinguished road

      0  

    Default Unanswered: Generated setter(getter?) messes w/ the property when it's an Ext.Element

    Unanswered: Generated setter(getter?) messes w/ the property when it's an Ext.Element


    Ext version tested:
    • Ext 4.07

    Description:

    If I create a class passing a config property of type Ext.Element, when I retrieve it w/ a generated getter, it comes out as something different. This doesn't seem to be happening in 4.1, but could you please share what is being done differently and if there's an easy way to avoid this situation?

    Code:
    Ext.define('MY.test', {
            config: {myEl: null},
            constructor: function(config){this.initConfig(config);}
    })
       
    var instance = Ext.create('MY.test', {
        myEl: Ext.getBody()
    })
        
    console.debug(Ext.getBody() == instance.getMyEl(), Ext.getBody(), instance.getMyEl())
    //outputs: false Ext.Element.Ext.core.Element Object

  2. #2
    Sencha - Support Team scottmartin's Avatar
    Join Date
    Jul 2010
    Location
    Houston, Tx
    Posts
    9,084
    Answers
    675
    Vote Rating
    467
    scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future

      0  

    Default


    Is there a reason you do not want to use 4.1? There are many issues that were correct from 4.07

    Regards,
    Scott.

  3. #3
    Ext JS Premium Member
    Join Date
    Sep 2007
    Posts
    55
    Vote Rating
    0
    mvarshavsky is on a distinguished road

      0  

    Default


    Scott - sure (please don't misconstrue my response as being emotional or whiny). I have very bad experience with upgrading sencha lib versions even when it's bugfix releases (e.g. Ext 4.0.x up to 4.0.7; or ST 2.0.0 to 2.0.1). I'd way rather deal with familiar issues that I've either fixed or worked around then re- test/write my application. Upgrading to a minor release is a risk our company can not afford.


    ...and are you implying this is fixed in 4.1?

  4. #4
    Sencha - Support Team scottmartin's Avatar
    Join Date
    Jul 2010
    Location
    Houston, Tx
    Posts
    9,084
    Answers
    675
    Vote Rating
    467
    scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future

      0  

    Default


    Please read my comments about 4.07 in your other thread:
    http://www.sencha.com/forum/showthread.php?229073


    ...and are you implying this is fixed in 4.1?
    This doesn't seem to be happening in 4.1
    It seems you have tested this and found it to be true?

    Scott.

  5. #5
    Ext JS Premium Member
    Join Date
    Sep 2007
    Posts
    55
    Vote Rating
    0
    mvarshavsky is on a distinguished road

      0  

    Default


    Sorry, for some reason I don't get notifications about replies on my threads. I think I tried on jsfiddle with 4.1 at the time to do a quick test to provide as much background for you guys as I can. The reason I've asked if it was fixed (despite seeing it work on 4.1) is because in my mind there's a difference between 'yes this was an issue and we addressed it' and 'can not reproduce'. Also, in the former case, there's a chance of finding exactly what's involved and comparing with my workaround.

Thread Participants: 1

Tags for this Thread