{"id":2903,"date":"2013-10-17T07:00:00","date_gmt":"2013-10-17T07:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2013\/10\/17\/what-is-the-inverse-of-adjustwindowrect-and-adjustwindowrectex\/"},"modified":"2013-10-17T07:00:00","modified_gmt":"2013-10-17T07:00:00","slug":"what-is-the-inverse-of-adjustwindowrect-and-adjustwindowrectex","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20131017-00\/?p=2903","title":{"rendered":"What is the inverse of AdjustWindowRect and AdjustWindowRectEx?"},"content":{"rendered":"

\nWe saw\n\nover a decade ago<\/a>\n(my goodness I’ve been doing this way too long)\nthat the\nAdjust­Window­Rect<\/code> and\nAdjust­Window­Rect­Ex<\/code> functions\ndo not take menu wrapping into account because they don’t\ntake a window handle parameter,\nso they don’t know what menu to test for wrapping.\nStill, they are useful functions if you aren’t worried about\nmenu wrapping\nbecause they let you do window size calculations without\na window handle (say, before you create your window).\n<\/p>\n

\nBut those functions take a proposed client rectangle\nand return the corresponding non-client rectangle\nby inflating the rectangle by the appropriate borders,\ncaption, scroll bars, and other non-client goo.\nBut how do you go the other way?\nSay you have a proposed window rectangle and you want to know\nwhat client rectangle would result from it?\n<\/p>\n

\nAdjust­Window­Rect<\/code> and\nAdjust­Window­Rect­Ex<\/code> can do that too.\nYou just have to apply a negative sign.\n<\/p>\n

\nThe idea here is that we use the\nAdjust­Window­Rect­Ex<\/code>\nfunction to calculate how much additional non-client area gets\nadded due to the styles we passed.\nTo make the math simple, we ask for a zero client rectangle,\nso that the resulting window is all non-client.\n<\/p>\n\n\n\n\n\n\n\n\n\n
−10<\/td>\n<\/td>\n0<\/td>\n<\/td>\n+10<\/td>\n<\/tr>\n
−50<\/td>\n<\/td>\n<\/td>\n <\/td>\n|<\/td>\n <\/td>\n<\/td>\n<\/tr>\n
<\/td>\n<\/tr>\n
 <\/td>\n <\/td>\n <\/td>\n<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n <\/td>\n<\/td>\n<\/tr>\n
0 —<\/td>\n<\/td>\n•<\/td>\n<\/td>\n<\/tr>\n
+10<\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/td>\n<\/tr>\n
<\/td>\n<\/tr>\n<\/table>\n

\nWe pass in the empty rectangle represented by the dot in the middle,\nand the\nAdjust­Window­Rect­Ex<\/code> expands the rectangle\nin all dimensions.\nWe see that it added ten pixels to the left, right, and bottom,\nand it added fifty pixels to the top.\n(Numbers are for expository purposes.\nActual numbers will vary.)\n<\/p>\n

\nFrom this we can perform the reverse calculation:\nInstead of expanding the rectangle, we shrink it.\n<\/p>\n

\nBOOL UnadjustWindowRectEx(\n    LPRECT prc,\n    DWORD dwStyle,\n    BOOL fMenu,\n    DWORD dwExStyle)\n{\n  RECT rc;\n  SetRectEmpty(&rc);\n  BOOL fRc = AdjustWindowRectEx(&rc, dwStyle, fMenu, dwExStyle);\n  if (fRc) {\n    prc->left -= rc.left;\n    prc->top -= rc.top;\n    prc->right -= rc.right;\n    prc->bottom -= rc.bottom;\n  }\n  return fRc;\n}\n<\/pre>\n
\nNote that the top and left are subtracted,\nso that the two negative signs cancel out.<\/p>\n","protected":false},"excerpt":{"rendered":"
We saw over a decade ago (my goodness I’ve been doing this way too long) that the Adjust­Window­Rect and Adjust­Window­Rect­Ex functions do not take menu wrapping into account because they don’t take a window handle parameter, so they don’t know what menu to test for wrapping. Still, they are useful functions if you aren’t worried […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-2903","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
We saw over a decade ago (my goodness I’ve been doing this way too long) that the Adjust­Window­Rect and Adjust­Window­Rect­Ex functions do not take menu wrapping into account because they don’t take a window handle parameter, so they don’t know what menu to test for wrapping. Still, they are useful functions if you aren’t worried […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/2903","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=2903"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/2903\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=2903"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=2903"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=2903"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}