I believe it's a bug because it started after upgrade from GXT 2.1.1 to 2.2.3.
I'm having a layout problem with this combination of components (the indentation indicates parent/child relationship):
ContentPanel (RowLayout and a ToolBar as top component)
ContentPanel (any layout, RowData(1, -1) to use components height)
Grid (RowData(1, 1) to fill space left in the parent panel
The problem is the grid height isn't beeing expanded to fill the parent's ContentPanel space left. I had to force height on the grid (100%) or else the rows doesn't show, but still the vertical space is filled only after a window resize.
I didn't test using another components.
I'm sending three attachments.
1. The window screenshot in version 2.1.1
2. Same window screenshot in version 2.2.3
3. A sample code to reproduce the problem.
Nothing was changed in my code, except GXT version, and from that upgrade the problem started.
Executing in host mode
Google Chrome 8.0.552.237
I did it by adding a WindowListener to the window and it worked. But seems to me this is just a workaround, not an actual fix, since I will have to add an WindowListener to all my windows using RowLayout.
First, is this the only solution?
Second, is this I reported a real bug?
Should I expect for a correction or use this workaround from now on?
So the support response so far is that this change was made due to "a bug with hidden items". (I don't know what that bug is, or what it's impact is).
The suggested solutions are:
1: Call layout(true) on the window after showing it
2: Roll back to the old version of RowLayout (be aware of the "hidden" bug)
3: Override the window class show() method to call this.layout(true) at the end.
I really think this bug should be addressed as it has compromised the Rowlayout should work.
Update: Sencha told me the "hidden items fix" was done because "The row layout did not always size the the panels in the rowlayout correctly if some of them where hidden."
Also option 1 and 3 above may cause so performance issues it you have complex windows.
Did they give you some indication that this bug will be solved in future releases? I don't think it's nice to be forcedto apply a workaround everytime I need to use RowLayout, unless they say "this is it".