Cast Away
4 discussion posts
Hi,
I'm a developper and I noticed my applications won't receive their WM_SYSCOMMAND WndProc (code &H112).
Especially those with the following m.WParam :
> &HF030 - Maximize
> &HF120 - Restore
> &HF032 - Maximze (from double clic)
> &HF122 - Restore (from double clic)
As soon as I close DisplayFusion, everything works as expected.
Please fix this behaviour, as this is really bad since you won't let any other applications get those very important WindowMessages for themselves.
You probably don't release the MyBase.WndProc(m) once you've used it. I would say you can do this within your own application (overiding a normal behaviour with your own and then blocking the WndProc), but not when it's a general sheel application like displayfusion is... causing others to be blocked!
Thanks a lot,
Cast
Are you using Monitor Splitting in DF by any chance?
I'm not 100% sure actually. I will check in with our devs to find out.
Ok, so you can disable application hooks for that specific application by creating a rule for it on the DisplayFusion Settings > Compatibility tab. The splits won't work for that application then, but it will still work for everything else.
Hope that helps!
Cast Away
4 discussion posts
Thanks Keith,
I will try that and come back to you to let you know
Cast
Cast Away
4 discussion posts
Working great!
Thanks a lot, that will work for me.
Cast
