Like others have said, "rethink your design". One thing to consider when you start destroying windows, is "memory-leaks" caused by stray objects left laying around.

The best strategy is to try to design your app, to create widgets once, then reuse them, by reconfiguring them as needed. If your layout fluctuates wildly from one selection to another, you might consider a menu at the top, with a frame underneath. You could have a graphic as the default view in the frame, and when a new selection is made, the graphic is shown, while the new window is built, and display it once done. You can build windows and frames while they are in a hidden state. They are not shown, until you "pack" them. Also there is "packForget" for removing something. So, for instance, in your display frame, when a new selection is made, you could "$frame->packForget", then reconfigure the frame, then pack it again. It can get tricky, but it can be done. Just remember to watch your memory usage as you test it. Nothing is more frustrating than getting something to run "like you want", only to find out later, that it jumps in memory 10 megs with every button click. :-( .....neccesitating a redesign.