From: Guillaume L. <gla...@te...> - 2003-11-26 14:49:31
|
On Wednesday 26 November 2003 12:53, Chris Cannam wrote: > I understand the impulse, but I don't believe any dialog is really > expensive to build these days. It's better to lag slightly when > calling for the dialog than to slow down normal use instead. Agreed. > I had actually assumed the audio manager was kept around so that when > you called for it again you got the same tree layout with the same > items visible and selected as last time around. If you have a lot of > audio segments, that could be a considerable advantage. True, but there's certainly a way in KDE to save the state of a tree. I suppose. > I'm beginning to think it doesn't. Stick a debug printout into the > DeviceManagerDialog destructor and it never turns up. And adding a > "delete this;" to the slotClose() slot does not appear to introduce a > crash. I'll take a look when I get home. > Yet the ControlEditorDialog's dtor definitely does get called > when it's closed. What extremely obvious difference between the two > am I overlooking? Doesn't one set the WDestructiveClose flag ? -- Guillaume http://www.telegraph-road.org |