I'm also a software developer for an app called VideoReDo. It's an MFC dialog based app. When it first launches it shows a "splash screen" which is a simplified UI with just an Open button. When it's in this mode we prevent the app from being resized or maximized by trapping WM_SIZE and WM_SIZING messages. Your app seems to override those messages and allows the window to be maximized even when it's in this mode. This creates all sorts of weirdness in the app as it has hidden controls and other things that are obscured by the limited size of the "splash screen" and that are only arranged and drawn properly once the "splash screen" is dismissed.

This seems to be something related to Windows and perhaps not your software. If I uninstall your software I can still maximize our software in splash screen mode if I drag it to the top of the screen. With your software installed I can double click the title bar to maximize, and I can't do that when it's uninstalled, but the fact that it can at all means it's something I need to fix. I'll look into dynamically changing the window style so it's not resizable at all in splash screen mode, rather then trying to trap the messages and see if that works.

Anyway you can ignore this post.

Actually this is still an issue on your end. I changed my app so it's not resizable at all (removed WS_THICKFRAME) and when I double click the title bar it still maximizes when DisplayFusion is running. It does not when it's not running.

Yes. That's the only reason I have Display Fusion. I have a Dell Untrawide monitor so I need to split it to make it usable. I was using Virtual Display Manager, but it caused weird clipping issues when maximizing some apps

This isn't Chrome, it's a program I'm a developer for called VideoReDo.

I can give you any infor,ation you need about the window. Which styles it's using, which messages it's receiving, etc... just let me know what you're looking for. Or if you want we offer a free trial and you can just install it and see what I mean.