 But after a couple of days, I finally found the issue and fixed it. It didn't happen, like I think a week after I originally recorded the video and honestly even though I really dig into the code, I couldn't find any clear issue. However, there has been some attempts by even viewers from this latest video, which is pretty cool, like the idea that somebody watches my video and then tries to fix it on their own. That's super cool, please do that if you can, makes me happy. But at the end, a solution wasn't very clear. So the idea was that each time a new window is added back to what is called again the proxy model, the model. Every time a new window is added back or removed from it, well it changes the count of the windows and that emits the count changed signal. And something shouldn't happen, in theory I contacted the person that wrote that piece of code, but I had no clear idea on how to fix it, so however I did find, let's say I work around, not a ugly one, to be honest, a pretty one, to avoid the flashing. So this bug has been fixed, it's no longer alive, I did it, it's no more. How did I fix it? So basically if you remember from the animation code, I might be too lazy to actually bring it up again and show it in KDN Live, but just go back like 10 minutes in the video, I'm sure you'll find it. If you do that, you will see that there are two animations that change the opacity. Basically when you go from opaque to transparent, it changes the opacity from 1 to 0, and when you go from transparent to opaque, it changes it from 0 to 1, which makes sense. Basically you're changing the opacity of the opaque layer based on whether it should be opaque or not. However by doing that, if it comes to the signal, you need to become transparent. And then just after that, also the signal to you need to be opaque. What happens is that it switches from one to the other to the first one, and it goes like, at the beginning it's opaque, so you've got this straight line, it's opaque. And then it says, okay, now you need to become transparent. And so it becomes to become transparent, which is going up like this. However, before it actually finished the animation, it says, okay, you need to become opaque again, just after that. And so it actually resets the opacity to be transparent, and then that's the cool animation. So you've got like this, tick, then flip. And that's the blinking you see. Now my hands are surely better than graphs I could do on Desmos. You totally understood everything, totally. But how did I fix it then? Basically I told him instead of going from 0 to 1, and from 1 to 0, just go from the current value you have to 1, and from the current value you have to 0. So basically this time, if we go, let's do this, if we go from 1, and then it tries to go to 0, and then it has to come back to 1. Instead of doing the whole whip thing, it just does this. And you almost don't see it, like you don't see it at all, because it's, I think, milliseconds. I don't know why even does it, but you don't see it anymore, because instead of resetting the opacity each time you need to go from one state to another, it just takes the whole opacity and animates that one. So now the bug has been fixed. It's no longer there. The fix ain't beautiful, I could have done better. But honestly, after a week of trying to fix this, let's say it, little bug, I was annoyed, and this was the best I could do, so I just went for it. So that was all. And of course, that doesn't end the bug fixing. I will find a new bug to bug fix. And just give me a second. I won't edit this part out, because at this point, you can be bored or whatever. I don't care. Yes, okay. Yes, I remember. There's this bug that I've been trying to fix, which is super annoying, which is when you, in the latest version of Plasma, when you go to the panel, you go into panel edit mode, and then you take an applet and try to change it to an alternative. For some reason, it just moves it all to the left. I've done some investigation, and it's super weird. I think I better understood how the code works. And honestly, I do not understand how the hell did it ever work, and now we'll have to fix it. And if I'm able to, I will do a devlog about this. Otherwise, I will just do a short video summarizing this time with pretty graphs and everything at the end how I managed to fix it, because I will totally fix it. That's for sure. I have just done like four videos in a row. I just sat here and recorded four of them. This is the last one. I don't know what order I will publish them by, but you know.