https://bugs.winehq.org/show_bug.cgi?id=57987
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #5 from Nikolay Sivov bunglehead@gmail.com --- (In reply to YuriK7 from comment #3)
Created attachment 78252 [details] Logs with propsheet debug channel
Here's the logs with +propsheet. Naively I would think that NULL is returned because the window was closed too soon for the DoCommand function ?
Yes, I think what happens is that Apply() involves calling back to the parent for notifications, and parent code has ability to destroy the dialog window. So what you get is WM_COMMAND (Apply) -> WM_NOTIFY to parent -> DestroyWindow/EndDialog -> WM_DESTROY cleans up -> return to the WM_COMMAND handler now with dialog data not longer available.
I think it safe to assume we have to check for nulls basically everywhere when calling back is possible. But let's do one change at a time.