Hey Antonio, Sorry for the long time getting back to you... but (as always), thanks for the test case.
2013/5/14 Antonio Mancina <[email protected]>: > One of the weirdest problems happened with a very simple widget displacement > within a two tabs tabmanager. I attach here the source tree ready to be > built from the build directory (cmake ../ && make). > > In order to trigger the problem, do this steps: > > - Click on "Container2" tab > - Click on "Container1" tab > - Click again on "Container2" tab > > At that point everything vanishes. If I comment the last code line (the > setMaximumSize directive), everything behaves properly. There was indeed a bug which I fixed just now in my copy (and needs more testing before pushing it out). However, the new layout API uses setMaximumSize() as a heuristic to resize the container based on the contents (up to the maximum size) rather than resizing the contents to fit the container size. The problem with set a maximum width is that CSS behaves strangely by default w.r.t. widths (they will automatically take the 'container' width), and this thus goes against the meaning of setting a maximum width for the layout manager. When changing the code to setMaximumSize(WLength::Auto, 2048), this behaves fine (even before the bug fix). What do you actually expect maximum width to imply in this case? Regards, koen ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
