 Well, the very first thing that happens whenever a new release is out is that we do get a lot of bug reports from users that actually try the new features and discover that they have bugs. And that's actually a very good thing. It would be even better if that happened in the QA before the release in the beta. Still it's very good that somebody do point out bugs after the release because that actually allows us to fix them. So a lot of bugs have been raised about the floating panel and I want to quickly go through them to explain what went wrong and what I'm going to try to do to fix them. So this is the first one, which is ugly margins around the floating, floating panel with any maximized window. This if I understood this correctly is a wheel and only bag. And it's not. Sorry. I was talking about another bug. This one is wheel and and X 11 and it was actually by design. That is when you maximize a window, you can see that all of the margin between the screen and the floating panel is occupied by the floating panel. And now I guess that people expected the panel to actually lower down and become a normal panel. It doesn't do that. It just expands and the idea behind that was one to actually make sure that all of the widgets remain in the same place. You don't want a widgets to move when you maximize a window because then you would have that if I just click this button, the buttons behind my mouse button, when I'm clicking then move to the left and to right, and that shouldn't happen. Now I could have tried to make sure that there was like less space occupied so that the panel actually moved down a bit. And originally that was the merger quest. However, that had some issues. That is, if I tile a window to the left, you can see that it has a healthy amount of margin underneath and above the panel and to actually have the panel only the float on the bottom. This top margin was unfeasible. So to have this top margin on tile windows, I had to actually make it default both ways and believe me. So the future what I'd like to do is make sure that when you actually tile a window to the left or to the right or both, the panel still deflows normally because if you have something like this as an example, the panel should not be floating because then you have this which is basically the same and it's not floating. In order to do that, you need to change the check from is anything maximized to either is anything maximized or piled or also another possible solution is to actually check if any window is colliding with the panel. Both of them are things that could be done and but they actually have to be implemented. And when that is done, it would allow the panel to actually go down a bit when it's defloting and that would make it much smaller when it's deflated. So that could be a possible solution. It wouldn't be the perfect one, but the issue is that it can't quite become a normal panel because that requires changing the size of the panel window and that's not quite something I want to do dynamically when you maximize or unmaximized windows broken corners. This one is very big and it also applies to floating panels and not only it has broken corners, but if you're using Weyland and you're using scaling, you will get a very weird back where the panel actually is bigger than it should be and exits the window. And that is due, I talked about it in a previous video too, that is due to the mask of the panel which actually sets the area that should be blurred and contrast affected being bigger than it should. It almost happens that the scaling is applied two times. So if you have 1.5 scaling, then it's applied one time and then another time. And that means that it will be 1.5 as an example times bigger than the panel itself. So blur and contrast effect is applied in an area which is bigger than the panel itself. Now I did propose a backfix that actually works. However, the K-Win developers didn't agree with the fact that it was the best approach. So now I'm trying to figure out with them how to properly implement this, but K-Win developers are very busy, so it's kind of hard to do this in a timely manner. However, that won't fix all of the bugs related to broken corners. This is in general a recurring pattern in KD Plasma as a whole. As an example, this back is only related to bottom left, bottom right and top right corners. If you have issues with the top left corner too, it means that it's unrelated to this. Then this is actually my favorite because it's a proposal, not a bug, and it's very simple to implement. And that is, you know that it unfloats when you maximize anything. This proposal says what about not defloating it if you're using how to hide, windows can cover and windows go below. Makes sense if you have like iOS-like dock that actually hides when you maximize anything and appears again if you put the mouse at the bottom to make sense for it to still be floating. So I think this is a very good proposal and it's also rather easy I think to implement. So big fan will totally do this. This one, lying around how to hide floating panel after making it visible over a full-screen window. This one was actually known when I did the merge request. It's another of those bugs that are wheeled only and require some help from Q-Win developers to actually fix them because the floating panel is actually doing this correctly. The code of the floating panel is correct. It's K-Win that is doing something wrong and it appears in particular fashion on the floating panel. You can see here that there is this line which is actually the shadow. So I am unable to draw a shadow around a floating panel. So whenever a panel is floating, the shadow is hidden. Whenever it defloats like this, the shadow appears again. So I actually have part of my code that says if the panel is floating then hide the shadow. If it's not floating then show the shadow. And this works. It works perfectly in X11. However, in Wayland, due to a Q-Win bug, when you hide the shadow and then you show it again, you cannot hide it anymore. So if you say again please hide it, it won't hide for some reason. And although the code is correct because I am asking the shadow to be removed, Q-Win is not actually removing it. So I need to figure out why Q-Win is doing this. And right now I have no clue whatsoever. So good luck me, I guess. Finally this is completely unrelated to the floating panel but it's the last bug that is in my short-term to-do list. So let's quickly go through it. And it's about corners in the header bar, in the plasmoid heading actually. That is, you do have this corner where you shouldn't have it as if the header was rounded. And it is indeed true that if you go see the SVG, the SVG for this is actually rounded. But it's a nine grid and if you don't know what that means, you should watch my playlist that I made about plasmoid theming because it explains that and how to actually make a plasmoid theme. This is part of the plasmoid theme. And if you have a nine by nine grid, it should be feasible to avoid that. So I need to look into that and see it's probably missing so some could actually make sure that the corner that should not be rounded actually isn't. Thankfully, it's not that noticeable by default. Can't even notice it. It's probably very small here. You can see there is some rounding by default. So it has to be fixed, but maybe slightly lower priority compared to all of the other stuff. So these are the bugs that I'm looking at right now. If I forgot any, you can just send me a message with a bug link that happens, but I will continue to look into them. So that was everything. And before you go, if you would like to actually help me out in fixing these bugs because I do this on my free time and currently I'm under exams from university. I have extremely little time and trying my best. If you'd like to donate something that would help me a lot. And by the way, thanks a lot to the people who are actually donating to me right now, even though I'm making a slightly less videos than usual. Again because of exams, I'm currently trying my best and I hope that's enough for you if it isn't. Sorry about that. See you tomorrow with another video.