Results 1 to 2 of 2

Thread: PR3 and the side effect of doing away with 'dockedItems'

  1. #1
    Sencha - Support Team keckeroo's Avatar
    Join Date
    Mar 2008
    Location
    Winnipeg, Canada
    Posts
    379
    Vote Rating
    11
      0  

    Default PR3 and the side effect of doing away with 'dockedItems'

    Hi all,

    Don't know if anyone else has run into this - and don't really know the benefit of lumping dockedItems into all the other items but ...

    .removeAll() now conveniently (?) removes ALL items in a component - including the docked ones.

    What happens when we have a panel with reusable toolbars and we wish to just replace the items and keep the toolbars intact without having to incur the cost of recreating the toolbars ?

    Any chance that Sencha could add a parameter to the removeAll so that we can keep the docked items in a component for re-use ?

    Thanks.

  2. #2
    Sencha User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,029
    Vote Rating
    1367
      0  

    Default

    I actually reported this earlier, it's a behavior change that isn't very welcomed IMO. What I do is execute getInnerItems() on the container which will return an Array of the items that aren't docked... Now I can iterate through that Array and remove() it from it's parent... until it gets fixed however they are going to do it.
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Frontend Engineer
    ________________
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:
    https://github.com/mitchellsimoens

Posting Permissions

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