When dynamically resizing windows at runtime using the is-maximized property, you can make a window extend beyond screen boundaries just a little bit if you remove the titlebar from a window that has one by default.
There are also some oddities with titlebar UI in vista. The borders never appear for a titlebar that was added to a window while it was maximized at runtime.
Numbered steps to reproduce this problem:
1) Make an interface file.
2) Make the window minimized, and give it a title bar.
3) Anchor a label to the bottom right corner
4) Anchor a second label to the top right corner
5) Put a single output in the window.
6) Run the following code snippet.
Code Snippet (if applicable) to Reproduce Problem:
The output should state: (with a resolution of 1280x800)
The output instead states:
When looking at a maximized window whose titlebar has been disabled, it seems to extend 3 pixels beyond the screen area on all sides. This accounts for our extra six pixels!
Does the problem occur:
Every time? Or how often? Every time with these parameters
On other computers? Yes.
In other user accounts? WTF? Yes.
When does the problem NOT occur?
When you instead add a titlebar to a window that previously did not have one.
Just found a new aspect to this bug. Apparently, giving the window a titlebar when it didn't have one before, and maximizing the window at the same time also has the same effect.
However, you can get around this by taking away the title bar immediately before you maximize the window, using two winsets instead of one.
Anchors also seem to be affected by this. If you add a window element with an anchor while there is no title bar, it will not reposition or resize properly when there is a title bar.
In general, title bars screw up positioning bad in vista.