1. #31
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,229
    Vote Rating
    114
    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


    Quote Originally Posted by ExtJSNinjas View Post
    I have a question that is related to the duplicate id messages that I was seeing earlier in this thread. When a control (and thus sub-controls) is destroyed, is it no longer unregistered from either Ext.AbstractManager or Ext.ComponentManager? This seems to be the case now.
    The destroy method does call the ComponentManager unregister method. Which is actually in AbstractManager.

    Do you have an example by chance that produces duplicate ids?
    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!"

  2. #32
    Sencha User
    Join Date
    Sep 2011
    Posts
    3
    Vote Rating
    0
    mkjellman is on a distinguished road

      0  

    Default


    i am also running into this problem. It looks like it is related to forms only.

    "Layout left connected: fieldset-1038<anchor>"
    "Layout left connected: fieldset-1081<anchor>"
    "Layout left connected: myformnamhere<anchor>"

  3. #33
    Ext JS Premium Member tvanzoelen's Avatar
    Join Date
    Apr 2008
    Location
    Groningen - Netherlands
    Posts
    1,108
    Vote Rating
    31
    tvanzoelen has a spectacular aura about tvanzoelen has a spectacular aura about tvanzoelen has a spectacular aura about

      0  

    Default


    You must tell the items how to anchor. Just setting the layout on 'auto' (of forms for example) is a quicker solution.

  4. #34
    Sencha User
    Join Date
    Sep 2011
    Posts
    3
    Vote Rating
    0
    mkjellman is on a distinguished road

      0  

    Default


    I have a "anchor: 'percentage%' on every item inside a container with a layout of type 'anchor' though, so i believe I already have told the items how to anchor

    auto doesn't layout correctly and in 4.0 this layout was fine. in 4.1 it renders correctly as well, just worried about the erorrs

  5. #35
    Sencha User
    Join Date
    Sep 2009
    Location
    Denver
    Posts
    51
    Vote Rating
    2
    McQuack_82 will become famous soon enough

      0  

    Default Workaround for layout errors in 4.1 beta

    Workaround for layout errors in 4.1 beta


    I was experiencing the same issues with the 4.1 version. I switched the layout to a column layout and it fixed the error coming up. I'm not sure why it happening but it seem to on show in the debug and not affect the rendering of the panel.

    Code:
     
         Ext.create('Ext.form.FormPanel', {
                title: 'Order Search',
                itemId: 'orderSearchFormPanel',
                region: 'west',
                width: 200,
                split: true,
                bodyPadding: 10,
                collapsible: true,
                layout: 'column',
                autoScroll: true,
                defaults: {
                    columnWidth: 1.0,
                    labelAlign: 'top'
                },
                defaultType: 'textfield',
                items: [
                    {
                        fieldLabel: 'Global Search',
                        name: 'global',
                        itemId: 'Global'
                    }
               ]
          });

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar