Results 1 to 4 of 4

Thread: AccordionLayoutContainer does not fill parent until window resize

Hybrid View

Previous Post Previous Post   Next Post Next Post
    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Oct 2012
    Posts
    2
    Vote Rating
    0
      0  

    Default AccordionLayoutContainer does not fill parent until window resize

    I've been banging my head against the wall for several days on this. I've viewed http://www.sencha.com/forum/showthre...h-parent-panel for the Ext Js library and verified that my accordion is the first child of a variable-height component. The layout works correctly after I resize the window, but not until then.

    I've attached some screenshots demonstrating the behavior. The "Stuff" panel is expanded in both of them.

    Joe
    Attached Images Attached Images

  2. #2
    Sencha User
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,737
    Vote Rating
    93
      0  

    Default

    You're referencing a Ext JS thread, but this is the GXT bugs forum - which library are you using?

  3. #3
    Sencha User
    Join Date
    Oct 2012
    Posts
    2
    Vote Rating
    0
      0  

    Default

    I'm using GXT, but presumably they're the same underlying widget. I've managed to work around this by calling forceLayout() when the tab is selected.

  4. #4
    Sencha User
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,737
    Vote Rating
    93
      0  

    Default

    The libraries are actually quite different, especially in GXT 3. While they have similar APIs, that is mostly due to following tried and true tactics of describing how to relatively size and position layouts, as well as other tasks like binding data, etc.

    GXT reuses some basic dom structure and styles from Ext JS, but generally implements them in a totally different way to as to take better advantage of the GWT compiler, and produce only the minimum about of code necessary for each browser, as well as the most efficient.

    Because the APIs are rooted in the same concepts, you may find that advice from one library applies to another, but because the implementations are so different, this will not always be the case.

    With regard to the forceLayout() method, this should only be needed when a change is made to the structure of the layout after the layout has been drawn once - GXT doesn't automatically assume that every change made requires an immediate update to the full layout, in order to prevent performance issues.

Posting Permissions

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