LGUG2Z / komorebi

A tiling window manager for Windows 🍉
https://lgug2z.github.io/komorebi/
Other
9.53k stars 192 forks source link

[BUG]: Stackbar doesn't respect UI scaling #1109

Open exiled-serenity opened 1 week ago

exiled-serenity commented 1 week ago

Summary

I use Komorebi on a work laptop, and as a result I am often working on different monitors. These monitors naturally have different UI scaling settings, but the stackbar is only sized with pixels and so doesn't scale with everything else. This results in a stackbar that will look too big on some monitors or too small on others, which no way to adjust besides restarting with a different configuration file. I would think there should be a way to specify some sort of relative dimensions, but there's no documentation indicating that.

Version Information

komorebic 0.1.29 tag:v0.1.29 commit_hash:818ac340 build_time:2024-09-28 01:48:31 +00:00 build_env:rustc 1.81.0 (eeb90cda1 2024-09-04),stable-x86_64-pc-windows-msvc

Komorebi Configuration

Not including the full thing, as it contains personal information. At the moment, the stackbar section is:
  "stackbar": {
    "label": "Process",
    "tabs": {
      "font_size": 64
    }
  }
This is great on 4K displays, but way too big on 1080p.

Hotkey Configuration

.shell powershell

# Reload whkd configuration
# alt + o                 : taskkill /f /im whkd.exe && start /b whkd # if shell is cmd
alt + o                 : taskkill /f /im whkd.exe && Start-Process whkd -WindowStyle hidden # if shell is pwsh / powershell
alt + shift + o         : komorebic reload-configuration

# Focus windows
alt + h                 : komorebic focus left
alt + j                 : komorebic focus down
alt + k                 : komorebic focus up
alt + l                 : komorebic focus right
alt + shift + oem_4     : komorebic cycle-focus previous # oem_4 is [
alt + shift + oem_6     : komorebic cycle-focus next # oem_6 is ]

# Move windows
alt + shift + h         : komorebic move left
alt + shift + j         : komorebic move down
alt + shift + k         : komorebic move up
alt + shift + l         : komorebic move right
alt + shift + return    : komorebic promote

# Stack windows
alt + left              : komorebic stack left
alt + down              : komorebic stack down
alt + up                : komorebic stack up
alt + right             : komorebic stack right
alt + oem_1             : komorebic unstack # oem_1 is ;
alt + oem_4             : komorebic cycle-stack previous # oem_4 is [
alt + oem_6             : komorebic cycle-stack next # oem_6 is ]

# Resize
alt + oem_plus          : komorebic resize-axis horizontal increase
alt + oem_minus         : komorebic resize-axis horizontal decrease
alt + shift + oem_plus  : komorebic resize-axis vertical increase
alt + shift + oem_minus : komorebic resize-axis vertical decrease

# Manipulate windows
alt + f                 : komorebic toggle-float
alt + shift + f         : komorebic toggle-monocle

# Window manager options
alt + shift + r         : komorebic retile
alt + p                 : komorebic toggle-pause
alt + r                 : komorebic cycle-layout next

# Layouts
alt + x                 : komorebic flip-layout horizontal
alt + y                 : komorebic flip-layout vertical

# Workspaces
alt + 1                 : komorebic focus-workspace 0
alt + 2                 : komorebic focus-workspace 1
alt + 3                 : komorebic focus-workspace 2

# Move windows across workspaces
alt + shift + 1         : komorebic move-to-workspace 0
alt + shift + 2         : komorebic move-to-workspace 1
alt + shift + 3         : komorebic move-to-workspace 2

Output of komorebic check

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\[USERNAME]

Looking for configuration files in C:\Users\[USERNAME]

Found komorebi.json; this file can be passed to the start command with the --config flag

Found C:\Users\[USERNAME]\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
LGUG2Z commented 1 week ago

I'm not interested in working on this (I don't have the hardware to reproduce) but I'll leave the issue open for someone who is.