Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

  1. #1
    Sencha Premium Member
    Join Date
    Sep 2011
    Posts
    48
    Vote Rating
    1
    stahlman is on a distinguished road

      0  

    Default Changes to config access

    Changes to config access


    In previous versions, I sometimes accessed config like this:
    this.someConfigProperty

    This no longer works. In 4.1, it appears that any of the following would work...

    1. this.getSomeConfigProperty()
    2. this.config.someConfigProperty
    3. this._someConfigProperty

    ...but I don't want to rely upon undocumented behavior (again). Method #1 is the only one I see mentioned explicitly in the docs, but for config used within methods called many times, I prefer a non-method access mechanism. Is #2 also safe?

  2. #2
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,293
    Vote Rating
    121
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Thanks for the report. This was the result of an incorrect merge from Touch 2 and we are going to restore the 4.0 semantics for configs as best we can. The only change I expect that will carry forward is that the default config value will be set via the setter to allow it to be (potentially) transformed.

    The impact of this is in the timing of the first call to the setter which might matter if your setting does things like navigate the component hierarchy (directly via ownerCt or indirectly via up/down/etc).

    You should not have to resort to _foo or getFoo: using getters for all property accesses is a useless overhead and inconsistent with (most) existing config properties in Ext JS itself. If you need to revert this for your testing, you can remove the "'_'+" from "internal: '_'+name" in ext-all(-debug). Look for "registerProcessor('config', function"...
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  3. #3
    Sencha User
    Join Date
    Mar 2008
    Posts
    24
    Vote Rating
    0
    michael.piecko is on a distinguished road

      0  

    Default


    I think you meant "registerPreprocessor('config, function'".

    Michael

  4. #4
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,293
    Vote Rating
    121
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    yeah... that one
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  5. #5
    Sencha Premium Member
    Join Date
    Sep 2011
    Posts
    48
    Vote Rating
    1
    stahlman is on a distinguished road

      0  

    Default


    Understood. Thanks. The workaround is helpful...

Thread Participants: 2