There are two cases: (A) Proxy is created first, dialog is created later on demand (B) Dialog is created and directly registers its window as proxy In (B) the dialog is usually on the stack and destroyed when the ArdourDialog instances leaves scope. In that case ~ArdourDialog() is called and the proxy remained. Destroying the proxy does destroy the registered window in ~WindowProxy() If ArdourDialog's d'tor itself deletes the proxy it would recurse into itself. Existing APIs e.g. drop_window() likewise delete the window and cannot be safely called from ~ArdourDialog.
4.6 KiB
4.6 KiB