> Actually, I just solved no. 1 and no. 3: I removed all resize() and > setMinimumSize() calls and used non-zero stretch factors everywhere:
Great - I will try with non-zero stretch factors. > A potential problem I see with your approach is structuring your code. For > instance, if you want to make a complex control (containing layouts) that you > want to re-use, would you derive your control from WLayout or from > WxxxWidget? In the latter case, you still get layouts within widgets. Yeah I understand - I think where I am is that you could use containers etc. if need be - but you would not normally need to because you would just use nested layout. > I never understand why GUI toolkits treat layouts different from widgets > anyway: why not have different container widgets that layout their children > in different ways? I don't mind layouts - but it would perhaps be cooler if they were plugin behaviours for widget containers. I.e. you *always* add children widgets to widgets [containers]. And for each container you can set the layout as a plugin. But other than adding some layout hints* you never interact with the layout after that. If you see what I mean. A. * And even that could be done via the widget itself ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
