Closed MartinodF closed 5 years ago
Totally understand your request and definitely agree with it, but I would prefer handling this by implementing https://github.com/i3/i3/issues/3721 and getting rid of the i3-gaps specific implementation. Would be good if you commented on there to mention this as well so it will be considered.
In the meantime I do not intend to change i3-gaps for this. Thanks for understanding!
If you want to temporarily patch this locally in i3-gaps, it should be as easy as doing this:
diff --git a/src/config_directives.c b/src/config_directives.c
index c78e7ba6..65306c24 100644
--- a/src/config_directives.c
+++ b/src/config_directives.c
@@ -681,7 +681,7 @@ CFGFUN(bar_verbose, const char *verbose) {
}
CFGFUN(bar_height, const long height) {
- current_bar->bar_height = (uint32_t)height;
+ current_bar->bar_height = logical_px((uint32_t)height);
}
CFGFUN(bar_modifier, const char *modifiers) {
Hi Ingo, thank you for your prompt feedback and for providing the patch! :1st_place_medal:
I understand your point, integrating this into i3 would be much better. I've commented on the i3 issue, let's hope this makes it upstream. Again, thank you and have a wonderful day!
I'm submitting a…
Current Behavior
i3bar height is interpreted as screen pixels. This leads to different bar heights on monitors with different DPI scaling.
Expected Behavior
i3bar height should be interpreted as pre-scaling pixels, and comply with the desired screen DPI scaling.
Environment
Output of
i3 --moreversion 2>&-
:I'm not sure how easy this change would be as I'm not familiar with the i3 codebase, but this is the only setting that I need to change between my machines, as the rest of the i3 config is shared without modifications.
I would like to implement it myself if that helps, but I would need a few pointers regarding how dpi scaling is usually handled in the codebase. How difficult would it be to implement?
Thanks!