Created attachment 107757 [details] No problem if it isn't on the edge however if it is on the edge than sub-menu appears on the other screen. With multiple monitor, If I call the right click standard menu near to the other screen (right side usually) as the standard menu right on the edge and I move to sub-menu then the sub-menu appears on the other screen. It's a problem either way, even if the monitor turned on. I tried a lot research without success and it's a very annoying little issue.
Can you explain why this is a problem? Why shouldn't the menu span screens? Isn't that why you have multiple screens?
Thanks for the prompt response, I think most of the people would agree that this behavior causes a mess on your desktop. Also a good example my current situation that I leave turned off my right screen most of the time or I watch videos full screen on it so I can't see the sub-menu or it's just annoying on the full screen streaming in this case. To explain more clearly, you want to use multiple screens because you want to be more organized, separate windows, applications, etc therefore they aren't mess up with each other. Actually I don't understand why is it questionable that this is a problem. It's clear, it's a problem and it's clear that nobody use multiple screen because the sub-menu from monitor 1 a cool appealing thing on the other application on monitor 2. If you guys think it isn't that important issue what should has been solved than I understand but I don't see the point why should we discuss unequivocal things.
Thanks for the clarification, I'll let the primary KWin developers take it from here.
Thanks! Also I'd note that kwin itself works based on the logic that the standard menu and sub-menu should appears the same screen where the application is. I see this when the standard menu doesn't touch the edge of the screen. I this case the sub-menu appears the other side of the standard menu and doesn't flow to the other screen.
What Qt version are you on? There used to be a bug in menu placement with multiple monitors that has been fixed. It might have also fixed this one as I cannot reproduce your issue.
These are unmanaged Windows which are explicitly not managed by the window manager -> not a bug in KWin.
Martin, if we accept that the behavior is undesirable, then it is *someone's* bug. Is this a bug on the app itself? Or something else? Also, is anyone else able to reproduce the issue with more recent QT and KDE Frameworks versions?
Qt Version 5.7.1 I'm confused, obviously. As far as I know, every windows managed by given window manager as you once stared the one you use. What the hack is unmanaged window? I mean there should be a more clear explanation. If it's true that it isn't a KWin bug then where should I try to ask to solve this. It's a frustrating issue, for example, I use my drawing pad focused on one screen only and obviously, because of this problem, I can't reach the sub-menu with it. Also I thought it isn't an application related issue however I tried more applications after you mentioned unmanaged windows and some of them works correctly, for example Thunderbird and Firefox. Interesting that I got this headache in all KDE application basically, KWrite, Krita, Konsole, KMail, Dolphin, etc.
In X there is a flag for Windows that they should not be managed. This is called either override_redirect or unmanaged. Menus are typical examples. It also means that the toolkit creating those windows is responsible for positioning them. In your case it is Qt and your issue is a known one. But your Qt version is also rather old.
Thanks for the explanation, Martin. That's the kind of info that bug filers are looking for when their bugs get closed without an obvious code change fix. Since this is resolved by an upstream Qt change, I'm changing the resolution status to UPSTREAM. Does anyone know what the Qt issue is? IF someone can add the URL for that, then people who experience this bug in the future can see what upstream change is necessary to get it fixed for themselves.
Could be https://bugreports.qt.io/browse/QTBUG-57160, which is fixed since Qt 5.9.