Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Microsoft"Docs" is not worth it's Name - it's a shame, what Microsoft creates (generates?) #1512
Desktop (please complete the following information):
Hi, @schittli, thanks for filing this GitHub issue; and my apologies for the issues themselves and my delay in responding. I'll describe the steps I've taken so far to address the issues, and the question that remains.
First, I update the conceptual topic Enable and control DWM composition to make it clear what the relationship is between a) the attribute flag passed to DwmGetWindowAttribute and DwmSetWindowAttribute, and b) the type of the attribute value that those functions retrieve/set. I added more code examples to that topic, include specifically a code example for DWMWA_EXTENDED_FRAME_BOUNDS, which was a scenario that you mentioned.
Next, I went through the three API reference topics below, and made sure the descriptions of each of the parameters/fields was clear, and I added a very prominent link (at the beginning of each of these three API ref topics) to the conceptual topic, so that readers would know from the start that code examples (and conceptual content) exist, and where to find them.
For the -32000 value that you mentioned, I also updated the third topic above, in the table row for DWMWA_EXTENDED_FRAME_BOUNDS, and I added this content, "If the window is minimized or otherwise not visible to the user, then the value of the RECT retrieved is undefined. You should check whether the retrieved RECT contains a boundary that you can work with, and if it doesn't then you can conclude that the window is minimized or otherwise not visible." I feel like that's a robust way of dealing with corner cases rather than checking for specific constant value, which it's safe to think of as implementation details.