Trying to destroy a panel is kind of “out there” IMO. Maybe that
“pig just don’t fly”, or, at least, fly with dependability in all
situations.
It's a heck of a lot easier to base a non-interactive message
display on a wx.Dialog with or without a timeout.
Try the first attached file on for size. The 2nd one demonstrates a
pop-up with user input, but also with a “deadman’s switch” timeout.
Oops ! Now that I think of it, shouldn’t wx.Timers be .Destroyed()
after their final use, though I’m not sure it matters in these
demos.
Ray Pasco