66f6168163
Don't assume the dialog is mode-less and call Destroy() from within a dialog method. This will most assuredly crash if the dialog is shown modally or quasi-modally. Don't leak memory for mode-less dialogs created on the stack. Make sure when the parent frame window is closed that all mode-less dialog memory is cleaned up. Dialogs are not child windows like controls and toolbars so their memory does not automatically get cleaned up when the parent window is destroyed. Do not directly access frame parent window's pointer in dialog destructors. Apparently the tear down order when destroying mode-less dialogs is not guaranteed so the parent window may get deleted before the dialog causing a crash when accessing the parent window pointer from the dialog dtor. Do not close mode-less dialogs in the parent frame's destructor. This doesn't guarantee that the dialog(s) will be destroyed before the parent but it may reduce some careless mode-less dialog event handling in the future. |
||
|---|---|---|
| .. | ||
| 3d_cache | ||
| 3d_canvas | ||
| 3d_model_viewer | ||
| 3d_navlib | ||
| 3d_rendering | ||
| 3d_viewer | ||
| common_ogl | ||
| dialogs | ||
| 3d_enums.h | ||
| 3d_fastmath.cpp | ||
| 3d_fastmath.h | ||
| 3d_math.cpp | ||
| 3d_math.h | ||
| 3d_viewer_id.h | ||
| CMakeLists.txt | ||
| credits.txt | ||