VuiMuich

Ooops, later apearently became _days_ later, sorry. Now I tried this, and it works so far: ```diff diff --git a/src/main.cpp b/src/main.cpp index 127c1dd..c66a7b8 100755 --- a/src/main.cpp +++ b/src/main.cpp @@ -32,7...

I have experienced this as well, when restarting eww due to a WM reload. Also sometimes these windows seem to have odd properties and size, not sure if this might...

On a side note: Using `pkill eww` currently is the 'clenaer' experience for me as doing `eww kill`. When I use `eww kill` I regularly end up with one of...

> Random thought came to my mind because `eww open bar && eww open bar` never had this problem i.e. when one waits for the other to finish. Only when...

So have a `initializing_lock` and the child has to wait before returning until the lock is gone as init finished?

You might want to search the issues, there has been some discussion about using `stalonetray` or `trayer` iirc.

I can confirm this. Also in my experience (I have split my bar into three windows) the windows get stuck individually and can be revived by closing and opening them...

I updated my `yuck` with these snippets: ```clojure (defwidget ws-layout [] (box :class "ws-layout" :space-evenly false :halign "start" :valign "start" :width 220 (box :class "icon-ws-layout" "") (box {wmstate.workspaces[0].layout ?: "n/a"})))...

The attempt from the last post is only a minor improvement, unfortunately. Though I learned, that it seems to be sufficient to enforce the a redraw of the `dock` type...

Oh right, that's a good point. Also the flag could be used when launching a daemon in order to assign the `id` at this point: `eww daemon -i 2 -c...