Results 51 comments of fogine

Looking at the code now. Its trying to focus the workspace which is lost (workspace 3 in your case) which is not possible so `i3wm` automatically creates a new workspace...

please try the new `1.0.1` release, it should be fixed.

fyi, I recreated the issue you described. I implemented a fix which makes sure active workspaces dont change on other display outputs on unplug event..

@antoyo could you test whether the issue still persists for the following git branch? https://github.com/fogine/i3-workscreen/tree/%239-fix-second-take

Hm, thats weird. If you unplug the monitor, you have single active display, right? In that case active workspace should be the same as it was before you unplug the...

I would expect this file [dvi_after_disconnect.txt](https://github.com/fogine/i3-workscreen/files/7557523/dvi_after_disconnect.txt) to contain: ``` { // workspace with 0 children "border": "pixel", "floating": "auto_off", "fullscreen_mode": 1, "layout": "splith", "marks": [], "percent": null, "type": "workspace" }...

In the new branch I cannot recreate the behavior you described (no new workspace is created when I unplug one of the two monitors). Could you also post the output...

Also can you try to temporarily disable the udev rule and after you unplug the hdmi, run `i3-workscreen` manually from terminal. Is behavior the same?

Ok, I cant recreate it on my machine. Could you apply the following patch, run `i3-command` manually after you disconnect the monitor and post the output? This should tell me...

Hm, ok last debug patch, then I'm out of ideas: ```diff diff --git a/i3workscreen/i3workscreen.py b/i3workscreen/i3workscreen.py index 3ba9699..542b38a 100644 --- a/i3workscreen/i3workscreen.py +++ b/i3workscreen/i3workscreen.py @@ -294,6 +294,9 @@ def main(): else: i3.command('workspace...