How to Adjust xcb Window Size for Client Area

Discover how to ensure your xcb window has the correct client area size by calculating additional margins to account for borders and title bars.
---
This video is based on the question https://stackoverflow.com/q/70975375/ asked by the user 'MarkaRagnos0815' ( https://stackoverflow.com/u/5706966/ ) and on the answer https://stackoverflow.com/a/71377680/ provided by the user 'MarkaRagnos0815' ( https://stackoverflow.com/u/5706966/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: xcb correct window size

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Adjust xcb Window Size for Client Area: A Comprehensive Guide

When developing applications with the xcb library in C++, managing window sizes can pose quite a challenge, especially when aiming to achieve a specific client area size. The problem typically arises when you want a window to appear with a certain width and height on the screen, while accounting for visual elements such as borders and title bars. This is an important aspect of user interface design, as it directly affects the layout and usability of your application.

The Problem with Window Sizes in xcb

When you create a window using the xcb_create_window function, the dimensions you provide refer to the client area of the window itself. This means that any decorations such as borders, title bars, and other visual elements are not included in the width and height parameters. Unfortunately, unlike the Win32 API, which provides a convenient function called AdjustWindowRect to automatically account for these additional sizes, xcb does not have a similar built-in way to get these dimensions.

This can lead to unexpected window sizes where the actual space taken up by the window on the screen is larger than anticipated. This guide will walk you through the steps necessary to compute the additional size needed to ensure that your client window has the expected dimensions.

Solution: Computing Additional Sizes

To address the issue, you can utilize the _NET_FRAME_EXTENTS property, which many window managers support. This property provides information about the size of the window decorations, allowing you to calculate the total space the window will occupy on the screen.

Step-by-Step Process

Create the Window: Start by creating your new window using the xcb_create_window function.

[[See Video to Reveal this Text or Code Snippet]]

Set Protocols and Properties: Set up necessary window properties such as WM_PROTOCOLS and window titles.

Listen for Property Notifications: You need to listen for property changes, particularly looking for changes related to _NET_FRAME_EXTENTS.

[[See Video to Reveal this Text or Code Snippet]]

Fetch the _NET_FRAME_EXTENTS Property: Once you receive the correct notification, retrieve the actual frame extents.

[[See Video to Reveal this Text or Code Snippet]]

Calculate the Margins: After obtaining the extents, you can compute the margins.

[[See Video to Reveal this Text or Code Snippet]]

Destroy the Window (Optional): If your process involves temporary windows, don’t forget to clean up.

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Managing window sizes can be tricky in xcb, but with the right approach, including the utilization of _NET_FRAME_EXTENTS, you can ensure that your client area matches your expectations. By following this guide, you can effectively create windows that not only look good but also provide a user-friendly experience.

If you have any questions or need further clarification, feel free to ask! Happy coding!