search

glzr-io / glazewm

GlazeWM is a tiling window manager for Windows inspired by i3wm.
GNU General Public License v3.0
5.12k stars 152 forks source link

[Bug] command to move window to a specific workspace not working #694

Closed rottakore closed 5 hours ago

rottakore commented 3 weeks ago

Describe the bug

The following code:

window_rules:
  - commands: ['move --workspace 2']
    match:
      - window_process: { equals: '(software process name)' }

do not work. I did some research in the problem and looks like it only affects some programs made with net framework (which the glazewm can't even put active or inactive borders in it, and windows 11 round corners don't work too), see an image below (can't show alot 'cause it's a program from my work): image

Reproduction

Write the code in config.yaml and try it.

Stack trace or error logs (if applicable)

no error.

Version number

v3.1.1

lars-berger commented 2 weeks ago

Is the program being tiled correctly by GlazeWM? Are you getting the move --workspace <WORKSPACE> command to work for other processes?

Some windows don't have a window frame (common for splash screens and games when you fullscreen them). The border is part of this frame, so it doesn't show up if a window has its frame disabled

rottakore commented 2 weeks ago

Yes, it's tiling and I can move when I use a keyboard shortcut with the same command.

rottakore commented 1 week ago

The weird is that this program opens in the primary monitor all the time when glazewm is not running (which is the workspace I want it to open), but with glazewm running, the program opens in the secondary monitor (workspace 1) all the time, doesn't matter if the command to automatically move it to workspace 2 is there or not