Created attachment 163290 [details] kwin placement & shadow SUMMARY When opening a bunch of konsole windows, I noticed kwin eventually got a little confused with placement, and then created a pretty ugly shadow in the position of the last few entries. Sorry - tough to describe, but hopefully the screenshot shows the issue. STEPS TO REPRODUCE 1. Open konsole 2. ctl+n a few dozen times
So the problem is that it stops cascading new windows after a while? What do you think it should do instead?
I would have expected that, yes - wouldn't you? Here's a sample of gnome, for what it's worth. Also, the drop-shadow density looks pretty ridiculous and poorly rendered, if the intent WAS to just keep opening them in the center).
Created attachment 163628 [details] gnome cascade
The cascading stops when there no more space to the bottom or right to fit the whole window. So what's the order behind the windows seen in the Gnome screenshot? It doesn't just go bottom-right forever; once it no longer fits on the initial diagonal line, where does it or where do you expect it to continue?
Created attachment 163675 [details] gnome_screencast I'm not advocating for copying gnome - if you feel the kwin behavior is expected, feel free to close. When I did the action, my perception was "wow, kwin got confused," especially given the fairly large shadow density. I almost questioned if the compositor crashed or something.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!