2010/1/5 Jimmy Kung <[email protected]>: > Hi, > > I encounter this problem and I think it might be related to the Wt framework. > I want to see if anyone can help me with it. > > Synopsis: When a WTreeNode is added to the WTree and then is removed using > removeChildNode() but without completely destroying the node and re-adds it > back to the WTree using addChildNode(), the select() / emit() signal > underneaths the node apparently is now duplicated. And each time the node is > removed and re-added the signal grows in a polynomial rate. >
Jimmy, I fixed two things: 1. if you click a selected node in single selection mode, unselect/select will not be emitted 2. the tree will disconnect its signal to the node when you remove it from the tree It is not allowed to add a node to a tree twice; in this case you'll still get multiple 'selected' events (among other things that will go terribly wrong). So in you proof of concept example, do not press 'Add' when the tree node is already visible. Fixes will be in public git soon. Best regards, Wim. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
