mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Taskbar is drawn over the komorebi-bar when it is placed on the left side of the screen #559
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rlopeznegrete on GitHub (Jan 16, 2025).
Summary
Hello,
I keep the windows taskbar on the left hand side of the screen. When the komorebi bar is loaded, it is always under the taskbar which cuts part of it off. Are there any settings I can play with that will fix this?
I have tried changing work_area_offset but this only causes the application windows to move, but has no effect on the size of the komorebi bar itself.
Thanks!
Version Information
komorebi 0.1.34
branch:master
commit_hash:129dc5d4
Komorebi Configuration
Hotkey Configuration
using default
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
"custom_layout" is now end-of-life
End-of-life features will not receive any further bug fixes or updates; they should not be used
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 fla
@LGUG2Z commented on GitHub (Jan 16, 2025):
I don't think this is a bug; if you are positioning your start bar on the left, you can use the appropriate configuration options for the bar to exclude that area - https://komorebi-bar.lgug2z.com/schema#position (you'll need to offset the start position )
@LGUG2Z commented on GitHub (Jan 16, 2025):
(There are also a bunch of changes coming to simplify the bar config - stay tuned! 🤞 )
@rlopeznegrete commented on GitHub (Jan 16, 2025):
aah I was able to move the bar as need! Feel free to close this issue as this is not a bug.
thanks!