Erik Hofman wrote: > No, removeChild isn't broken, the GUI code was broken.
Erik, you seem to have missed the point. Sorry, but this call is definitely bugged. Call removeChild() on a node, fetch the node again, it should return null, but you get the old node even after it was removed. > The removeChild() code was used because "we" wanted the dialog to appear > with the same dimension and location after loading the configuration > file again. But we don't do that anymore, the settings remain in the > property tree so the removeChild calls should have been removed back then. This is wrong. How does one have a dialog with fixed layout for some parts and dynamic layout for others? The whole point was to restore the property tree to the state that it had before the layout was performed. Can you provide more specifics about your change? I strongly suspect you've broken the intended behavior with this change. Andy _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
