I can now! Because of frustration at working out how to give example code here - so folks can help debug (and to see if I am just being very stupid! - or if there are issues). I have put all my code on a publicly available Subversion repository with a web viewer.
So if you look here - http://svn.open-bpm.org/ and go under herchosting -> trunc -> console. You can also pull the code from svn://svn.open-bpm.org/herchosting/trunc/console with a subversion client. I am still working on the print.cpp bit trying to get the treeview column 0 header and widths to work under IE7 (seems fine under firefox). Adrian 2009/5/14 Rogier Schouten <rogier.schou...@besi.com>: > Hi Koen+Adrian, > > I'm currently also experiencing this problem (wanting to use the 3rd > scenario below). Otherwise, witty is indeed fantastic of course :) > > Koen, is this going to be implemented anytime soon? > Adrian, can you give me a code sample for your solution? > > Regards, > Rogier > > > > -----Original Message----- > From: Adrian Sutherland [mailto:adr...@sutherlandonline.org] > Sent: dinsdag 5 mei 2009 11:22 > To: witty-interest@lists.sourceforge.net > Subject: Re: [Wt-interest] WStackedWidget > > Hi Koen > > Thanks for your reply. > > 2009/5/5 Koen Deforche <k...@emweb.be>: >> Hey Adrian, >> >> You are right that WStackedWidget does not actively manage the size of >> its children -- it simply shows() one of multiple child widgets, and >> uses HTML/CSS default layouting rules (which indeed are not entirely >> consistent among browsers, especially w.r.t. vertical sizes). >> >> What kind of behavior are you looking for (what is your use-case) ? > > Firstly, not really being a Web expert - what I decided to do with CSS > is to only use it to set font/colours and the like, and use Wt layout > managers for positioning. Seemed a good compromise to keep the > "developing an application" development style, if you see what I mean. > > What I expected was that WStackedWidget would act just like any other > widget - like WText say. Esp. if it is in a Layout then it would be > resized by the layout - and therefore resize its children (i.e. your > third scenario). I think scrollbars are not needed - as you can always > use WScroll (or whatever it is called) round each child as need be. > > Without this I think that Menus and Tabs (which use Stacked Widget) > will not be useful unless you use CSS for positioning (?) > >> Perhaps this is what you are >> looking for? > > Right :-) > >>> Anyway any hints welcome - I feel a bit depressed at the thought of >>> having to manually implement some kind of menu (removing (or hiding) >>> child widgets in some kind of home grown way, but I guess I will have >>> to try this :-( >> >> I hope not. In any case, it looks like a very useful feature to make >> the stacked widget play better together with the layout managers to >> implement the 3rd scenario. > > I did this in the end - wasn't too bad (once its done its done) - just > used anchors in the same way that WMenu does. But it has longer code > and its not so easy to add menu items. Also I have avoided using Tabs > which would have been nice. > > I'm enjoying using Witty - its fantastic in fact. > > Adrian > > ------------------------------------------------------------------------ > ------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks > to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > witty-interest mailing list > witty-interest@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/witty-interest > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > witty-interest mailing list > witty-interest@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/witty-interest > ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
