22.09.2025, 10:52 PM
(This post was last modified: 22.09.2025, 10:54 PM by Gary Beene.)
Howdy, Jules!
Yes, I see that too.
Playing with it, I noticed that the entire restored dialog is transparent - not just the "hole".
Can we detect when the dialog is restored, then take action?
This code detects when the app restores so perhaps we can add something there to reset the dialog?
This seems to work - by restarting the app after a restore takes place. It's a bit of a sledge-hammer approach, but does seem to work. Surely there is a feather-touch solution!
The message WM_WINDOWPOSCHANGING might be another place where we can detect a restore.
Yes, I see that too.
Playing with it, I noticed that the entire restored dialog is transparent - not just the "hole".
Can we detect when the dialog is restored, then take action?
This code detects when the app restores so perhaps we can add something there to reset the dialog?
This seems to work - by restarting the app after a restore takes place. It's a bit of a sledge-hammer approach, but does seem to work. Surely there is a feather-touch solution!
Code:
Do this ...
Dialog Show Modal hDlg, Call DlgMain
If Restart Then pID = Shell(Exe.Full$,1) 'restart the app
And this ...
Case %WM_SysCommand
Select Case Cb.WParam
Case %SC_Restore
Restart = 1
Dialog End hDlg
End SelectThe message WM_WINDOWPOSCHANGING might be another place where we can detect a restore.