Only downside is that I have to wait about 45 seconds after login to do anything or else the layout gets screwed up and the window focus gets hijacked by new spawning apps and workspaces.
It seems this method also has those issues.
sway-layout does not enforce any dependencies between apps. everything is started concurrently, so unless your apps manage their own interdependencies, it's not going to work
on the other hand, that means the initial wait should be much shorter
one potential avenue you could explore might be to configure a headless output, and try to have your slow starting apps/workspaces anchored there until they are ready. I haven't trie it though...
tombert•2w ago
This isn’t a huge issue for me, and I did have a lot of fun overengineering my Swaybar, but I still think it should at least optionally come with some sensible default, like the system clock being added by default.
awithrow•2w ago
On the plus side, I've gotten a much better understanding of all the moving pieces under the hood. It's also been a good excuse to migrate to some new tools which spark more joy than the old ones
tombert•2w ago
I probably wouldn't try to sell my parents on it though.
[1] https://git.sr.ht/~tombert/swaybar3
[2] https://git.sr.ht/~tombert/rs-sway-prog-switch