Multiple window rules: with "then move" "then assign_workspace" not executed
Open
Nobody has claimed this yet.
bug
low-priority
PRs-welcome
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 237
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
With those window rules
rule_3 = on created if app_id is "qterminal" then assign_workspace 1 0
rule_4 = on created if app_id is "qterminal" then resize 1924 1022
rule_5 = on created if app_id is "qterminal" then move 0 10
Application will open always on current workspace. Tested also for org.kde.kcolorchooser.
To Reproduce
- Assign "move" and "assign_workspace" (and eventually more rules) to an application
- Open it
- It will not respect "assign_workspace"
- comment "move" rule
- open application, it will respect workspace again.
Expected behavior
All rules are respected.
Screenshots or stacktrace
Wayfire version
0.8.0, git, branch alpha-add-ipc
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported window-rule sequence with qterminal or org.kde.kcolorchooser, including assign_workspace, resize, and move. Trace the window-rule handling for created applications and compare behavior with the move rule removed. Done means all listed rules are applied and the application opens on the assigned workspace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100