Closed lilacpixel closed 1 year ago
It looks like a bug in the go-sway library. A floating node treated this way (at least viewed through go-sway) no longer has AppID
or PID
, and my code was not ready for this. I added a workaround, that skips such tasks while crating the task list. They will be invisible to the dock, however.
Could you build and install from the fix35
branch, and tell me how it behaves on your side?
fix35
branch is working perfectly! I don't use floating windows in this way very often—just a weird edge case that I thought was worth reporting, but it's awesome to have it fixed so quickly! Thank you so much! As a macOS switcher, I couldn't be more thrilled to have a beautiful dock like this for sway :smile_cat:
Haha! I admit it gave me a headache. But I fixed 2 more issues by the way.
As a macOS switcher, I couldn't be more thrilled to have a beautiful dock like this for sway
There's also a Hyprland version. After years on sway, I finally find Hyprland more flexible. All my stuff is currently being ported to Hyprland, most part is ready to use.
BTW: pull the latest commits, just in case you're out of date. I'm not merging tonight, it needs some more testing.
Describe the bug If a floating window is split horizontally or vertically, nwg-dock crashes with the following output:
It's referencing the folder where I compiled the application, which, of course, no longer exists. I'm not sure why it might still be trying to access anything in this folder after compiling and installing.
The same crash occurs when attempting to launch nwg-dock when a split floating window already exists.
To Reproduce
Expected behavior nwg-dock should not crash, nor should it attempt to access the compile-time directory after being compiled and installed.
Desktop (please complete the following information):
Thanks for taking a look! ☺️