![]() * Bug report for KDE, active 2004-2012: with comments from the devs that there are no plans to fix the spec since Wayland is coming * Bug report for KDE, active 2008-2012: with a patch that was ignored because KDE5 was coming * Related config option from tint2 (strut_policy): 35) or percentage (e.g.Some further documentation on this issue: Tray offset defined as pixel value (e.g. By default the tray container will use the bar NOTE: A center aligned tray will cover center aligned modules If empty or undefined, tray support will be disabled Modules-right = coregraph ramgraph lan-network Modules-left = appmenu dk-workspaces dklayouts I just use polybar, and tried to set it up for each monitor like I do with bspwm: Interested to see what you come up with (but that should probably be another thread). You planning to use a status bar like polybar? I have yet to figure out how to get polybar to function properly on two monitors with dk. ![]() Your rules look right, maybe try mon1, mon2 instead of the actual monitor name. I have not tried to open an application on a specific monitor and open on the current workspace. Then I open applications on a specified workspace and have them grab focus - # open window(s) on a specific workspace (assigned monitor)ĭkcmd rule class="^gimp$" ws=6 focus=trueĭkcmd rule class="^firefox$" ws=4 focus=true # assign workspaces to monitors (requires static_ws=true) This is what I have for the workspaces: # use static workspaces (not default) & logfile="$HOME/.local/share/xorg/dkrc.log" # example dkrc to show some basic command usage and error reporting I am not sure I have the monitor bit at the bottom correct or not. certain apps to open on workspaces 1-5 others 6-7.10 workspaces - 5 on HDMI-A-0 (monitor one) 5 on DisplayPort-0 (monitor two).How are you guys handling multi monitor with dk?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |