Skip to content

Conversation

@patrick96
Copy link
Member

Since i3 4.22 now supports gaps, negative gaps can cause nodes (workspaces, windows, ...) to have negative coordinates which we did not support.

However, sometimes i3 reports negative coordinates as uint32_t. Because of this the range of possible values for rectangle coordinates are [INT32_MIN, UINT32_MAX).
To work around this, we just read an int64_t.

Ref: i3/i3#5352
Ref: polybar/polybar#2888

Since i3 4.22 now supports gaps, negative gaps can cause nodes
(workspaces, windows, ...) to have negative coordinates which we did not
support.

However, sometimes i3 reports negative coordinates as `uint32_t`.
Because of this the range of possible values for rectangle coordinates
are `[INT32_MIN, UINT32_MAX)`.
To work around this, we just read an int64_t.

Ref: i3/i3#5352
Ref: polybar/polybar#2888
@patrick96 patrick96 merged commit 85b444c into polybar:master Jan 5, 2023
@patrick96 patrick96 deleted the negative-rect-coords branch January 5, 2023 21:00
patrick96 added a commit to patrick96/polybar that referenced this pull request Jan 5, 2023
patrick96 added a commit to patrick96/polybar that referenced this pull request Jan 5, 2023
patrick96 added a commit to patrick96/polybar that referenced this pull request Jan 5, 2023
patrick96 added a commit to polybar/polybar that referenced this pull request Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant