Hello all, Not being all that au fait with either WT or QT (although working with WT has made me determined to attempt my next desktop app. in QT) I would like pass my strategy before vastly superior eyes.
I have a witty app. which is designed to use cascading WTabWidgets (2 levels deep at the moment), it looks similar to the layout in the witty class reference. Each tab represents an "applet", usually a form. As I change from tab to tab my applets remember state which is great but at certain points, typically after a form submit, I would like to reset the applet on the next view, not immediately. What i am currently doing is this, in each applet class I have a signal called "invalid" which I emit when I want the applet reset. Then in the class that holds the WTabWidget I respond to the signal by setting a field in a bitset to false/0 (the bitset reflecting the validity of the applets). In a member function that is called when WTabWidget::currentChanged is emitted I use the index parameter to check whether the corrresponding applet needs to be reset and respond accordingly. If I do reset the applet I clear() the container and then add a new copy of my class and reconnect the invalid signal. I hope this is all clear and I would appreciate any feedback anyone can give me on whether I am barking up the wrong tree. I'd like to say again that I am really enjoying working with witty and I am learning a lot fast :) Cheers, Brad Hubbard ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
