Wrong window geometry of tiled windows (xwininfo)
When using xwininfo to get geometry information about a tiled window, the y_offset is always reporting to be 0.
Let's consider this example:

When using xwininfo to get the get information about the editor (window at bottom left):
phisch@tower ~ xwininfo -id 54525953
xwininfo: Window id: 0x3400001 "Untitled-1 - giph - Code - OSS"
Absolute upper-left X: 200
Absolute upper-left Y: 200
Relative upper-left X: 200
Relative upper-left Y: 200
Width: 1358
Height: 1240
Depth: 24
Visual: 0x21
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x20 (installed)
Bit Gravity State: NorthWestGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsViewable
Override Redirect State: no
Corners: +200+200 -3562+200 -3562-0 +200-0
-geometry 1358x1240+200-0
The absolute and relative x and y offsets reported at the top are correct. The geometry string at the bottom reports 0 for the y_offset.
When the window is in floating mode, the y_offset in the geometry string is correct:

phisch@tower ~ xwininfo -id 54525953
xwininfo: Window id: 0x3400001 "Untitled-1 - giph - Code - OSS"
Absolute upper-left X: 200
Absolute upper-left Y: 200
Relative upper-left X: 200
Relative upper-left Y: 200
Width: 700
Height: 400
Depth: 24
Visual: 0x21
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x20 (installed)
Bit Gravity State: NorthWestGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsViewable
Override Redirect State: no
Corners: +200+200 -4220+200 -4220-840 +200-840
-geometry 700x400+200+200
Besides that, in my second example it is also clear, that the Corners values are completely off.
I am not sure if this is a bspwm or xwininfo issue, but since there has been an issue here before that seems related (#575), i guess this might be a bspwm issue.
Did you ever figure out a workaround? Dealing with the same issue.
@intr-cx no, and haven't used bspwm in a couple years
@intr-cx
a workaround?
Why not just use Relative upper-left{X,Y} and Width & Height to calculate geometry? xwininfo gets those via a simple xcb_get_geometry
@ortango
Why not just use Relative upper-left{X,Y} and Width & Height to calculate geometry? xwininfo gets those via a simple
xcb_get_geometry
Seems I should get my eyes checked, or just a classic case of tunnel vision. Thanks!