-
-
Notifications
You must be signed in to change notification settings - Fork 694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: internal/i3 padding is removed, except on the left side for most recent label on second monitor when using pin-workspaces #3024
Comments
The following is logs that show what happens when padding is set to 0 for all states. This is separated into a file per monitor. rdp0 had windows 0 and 1 and rdp1 had windows 2 and 3.
|
Results of xrandr:
|
Padding 0This is what I notice in the logs based off my actions for padding 0 for all states For rdp0
For rdp1
Padding 4This is what I notice in the logs based off my actions for padding 4 for all states For rdp0
For rdp1
|
Final note, I tried this with 3 monitors with xrdp output as follows:
I can confirm that this issue will happen on both of the 2 monitors without the focused window. I can provide more logs for this scenario if desired. |
Was an issue with my config. Missed the visible option. May reopen to update documentation to explain that visible is the equivalent of the i3 "client.focused_inactive" state. |
Checklist
Steps to reproduce
I usually run through a startup script that kills all instances of and restarts polybar. The commands are as follows, with logs having been added for sake of debugging.
This error does occur when running without the monitor options, which obviously only creates a bar on a single screen when there are multiple monitors. The issue doesn't occur when running on only a single monitor.
Minimal config
Polybar log
This is separated into a file per monitor. rdp0 had windows 0 and 1 and rdp1 had windows 2 and 3.
Expected behavior
Suppose my label-focused, label-unfocused, label-occupied are all the same and have the exact same padding of 4. monitorA contains i3 windows 1-2-3 and monitorB contains i3 windows 4-5-6.
Suppose 2 is focused. monitorA polybars i3 module should look like this ignore the lack of background color, one can imagine it doesn't have background. I am using spaces to represent padding and the top is polybar on monitorA and the bottom is polybar on monitorB
1 █ 2 █ 3
4 █ 5 █ 6
If I switch from 2 to 5 it stays the same
1 █ 2 █ 3
4 █ 5 █ 6
If I switch from 5 to 2 it stays the same
1 █ 2 █ 3
4 █ 5 █ 6
If I now change to 3 it stays the same
1 █ 2 █ 3
4 █ 5 █ 6
Move window 3 to monitor 2
1 █ 2
3 █ 4 █ 5 █ 6
Actual behavior
Suppose my label-focused, label-unfocused, label-occupied are all the same and have the exact same padding of 4. monitorA contains i3 windows 1-2-3 and monitorB contains i3 windows 4-5-6.
Suppose 2 is focused. monitorA polybars i3 module should look like this ignore the lack of background color, one can imagine it doesn't have background. I am using spaces to represent padding and the top is polybar on monitorA and the bottom is polybar on monitorB
1 █ 2 █ 3
4 █ 5 █ 6
When I switch from screen 2 to 5 the padding around 2 is removed but one unit of padding remains in front of it
1 █ 2█ 3
4 █ 5 █ 6
If I switch from 5 to 2 the padding around 5 is removed but one unit of padding remains in front of it
1 █ 2 █ 3
4 █ 5█ 6
If I now change to 3 it stays the same
1 █ 2 █ 3
4 █ 5█ 6
Suppose window 3 is now focused and 2 was the most recent focused on monitorA aside from 3. If I move 3 to monitorB it now looks like this, with the space around 2 being removed except one unit in front:
1 █ 2
3 █ 4 █ 5 █ 6
Whichever the last focused label was on the monitor that does not have an active label always has no padding behind and one unit of padding in front.
Window Manager and Version
i3 4.22
Linux Distribution
Arch (Hosted through Hyper-V and run through RDP)
Polybar version
Additional Context / Screenshots
In this video I use the following config:
I can't take video across multiple monitors. This was taking using snipping tool from windows. I am using rdp and hosting my linux vm on windows, which should be inconsequential to this bug, but possibly of note. For context, I went from 1 to 0 to 2 to 0 to 3 etc in the first video and 0 to 1 to 7 to 1 etc in the second video.
https://github.com/polybar/polybar/assets/44072946/9a0f3d5d-d8c1-4a2f-821a-791c77bef04e
https://github.com/polybar/polybar/assets/44072946/3f3e76fb-220f-40d6-8ce8-60df40af1d4c
In this next video I've increased the size of the padding to 4 with everything else the same as above. I also move some screens from one to the other and create new screens in this to show how it's being affected. It only shows one monitor. I do the following:
polybar_issue_wider.mp4
The text was updated successfully, but these errors were encountered: