You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, there is screen.workarea property in API. But third party applications cannot get this value in easy way.
For example I want to run rdesktop -g workarea as manpage says:
-g <geometry>
Desktop geometry (WxH). If geometry is the special word "workarea",
the geometry will be fetched from the extended window manager hints
property _NET_WORKAREA, from the root window.
Expected result is rdesktop window which covers desktop without wibox, but actual is fullscreen window.
The text was updated successfully, but these errors were encountered:
We stopped setting _NET_WORKAREA in commit 9c02087 because, well, what should this property be set to in a multi-screen configuration?
The problem is that _NET_WORKAREA has to describe the workarea of all screens, so you cannot really compare this with screen[1].workare.
If you have a good idea on what to do here, feel free to say so. Otherwise I'll keep claiming "the standard is unimplementable".
There are no _NET_WORKAREA EWMH for Awesome's root window. For comparing, this is part of
xprop -root
dump in Openbox:Yes, there is screen.workarea property in API. But third party applications cannot get this value in easy way.
For example I want to run rdesktop -g workarea as manpage says:
Expected result is rdesktop window which covers desktop without wibox, but actual is fullscreen window.
The text was updated successfully, but these errors were encountered: