Wiki Link: [discussion:3385]
Resizing issue from previous Version 

May 11 2010 at 12:24 AM

We implemented the previous version of the library in our WPF app in order to create a custom title bar. When released to our test client base we had reports of issues with resizing on a second monitor (I'm trying to track down the exact description of the problem and will update this discussion once I do). This only happened for about 5% of users and was not something we could recreate internally, but was recurring and forced us to come up with our own solution (which isn't 100%).

My question is - With the limited info I've provided, do you have any idea as to whether or not that bug will continue to happen with the latest version? If so, would it be something we could work with you to resolve?

I know it's tough to answer without more specific info, but my hope is that something may have changed in the latest version that would correct this behavior.


May 11 2010 at 10:30 PM
Can you describe what kind of symptoms you were seeing (e.g. cursor didn't change over resize edges, window stopped resizing after a certain point?), or what you did to work around it?

One thing with the old version of the library was that it replaced the Window template with one that had a Canvas as its root and databound Width and Heights. That sometimes caused some weirdness in some scenarios. Also on multimon Win7 setups there tended to be an issue that would cause the glass to turn black, but that only affected DWM content.

Without anything more specific I can only speculate what was happening.

May 12 2010 at 4:42 PM
I've emailed the full issue to you as I can't include attachments in this discussion. For anyone following this discussion, here is an overview of the behavior that we experienced:

When on a machine with dual monitors (with varying resolution, specifically the main monitor is smaller than the second) some times the window gets cut off when attempting to maximize to the second monitor. It's a very particular bug but prevented us from using the original Shell Integration Library in production, as an alternative we ended up using a custom solution where we have no title bar and create our own, however, when the window redraws on the screen it needs to draw to the whole screen size and then adjust for the taskbar which causes a flicker, it also means that we can't have the exact style that we would like on the window itself.

May 12 2010 at 5:22 PM
Update for those following along at home...

So probably what this was related to was handling WM_GETMINMAXINFO, which is required if you use WindowStyle.None and want your maximized window to not obscure the taskbar. There can be some edge cases that are tricky to handle when you do this.

With the window chrome library, generally you shouldn't need to use WindowStyle.None. By not setting that WindowStyle there's no need to handle WM_GETMINMAXINFO.

Jul 19 2012 at 1:47 AM
Was a solution for this ever found?

Page view tracker