Summary: | Require that screens are touching | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | srgames |
Component: | kcm_kscreen | Assignee: | David Redondo <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aleixpol, eaton.mark, kde, nate, plasma-bugs, postix, xaver.hugl |
Priority: | HI | ||
Version: | 5.24.5 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=459744 https://bugs.kde.org/show_bug.cgi?id=449140 |
||
Latest Commit: | https://invent.kde.org/plasma/kscreen/commit/f95cbe13d347f74a8b53f0ff2a6e28def8e8529f | Version Fixed In: | 5.27 |
Attachments: | picture showing where the invisible border on the main screen is beginning |
Description
srgames
2022-05-17 08:32:24 UTC
Yeah, when the screens aren't exactly touching in the config UI, you can't move your cursor between them. I don't think this is a good design; a gap between screens shouldn't prevent any screens from being inaccessible with the cursor. Or, if that's not the intended design, it's a bad bug. :) This is in part a symptom of https://invent.kde.org/plasma/kscreen/-/commit/cc832fd4296440fcd9298cb03b0cc736a99ed8bb. That's not to say this is not a problem, I am not sure what the right solution here is, besides making floating screens never the case. For non-touching screens, could we internally make an invisible area that the cursor can go on that bridges them together? I think I have to clarify, sorry. It's my first bug report. :D The border from right screen to left left screen is "normal" for me as this was the same when I was still using Windows. The border on the main screen in this case though prevents me from moving the window (on the right main screen) above the point where the second screen "docks" on the left side, even though there is enough space. With the mentioned launcher there is a hard border I can't cross dragging the launcher further up, it stops right there (where the secondary left monitors top is "docked"). Other windows have a similar behavior, but a "soft" version of it. There is a noticeable, invisible border dragging them over the point upwards (and also back down) but they kind of "clamp" on it for a short time and then jump over it. This is also annoying but at least I can get over the point. (In reply to Nate Graham from comment #1) > Yeah, when the screens aren't exactly touching in the config UI, you can't > move your cursor between them. I don't think this is a good design; a gap > between screens shouldn't prevent any screens from being inaccessible with > the cursor. There's a problem - how would you prevent the pointer going outside the screen into nothing? I think it's a kscreen bug, it should not allow applying output configurations with gaps between screens. That's fair, we could do that too. *** Bug 459745 has been marked as a duplicate of this bug. *** *** Bug 392152 has been marked as a duplicate of this bug. *** *** Bug 392153 has been marked as a duplicate of this bug. *** *** Bug 422073 has been marked as a duplicate of this bug. *** Git commit f95cbe13d347f74a8b53f0ff2a6e28def8e8529f by David Redondo. Committed on 21/11/2022 at 09:49. Pushed by davidre into branch 'master'. kcm: Do not allow configs with gaps between screens That creates problems for users, things render into the void or unable to move mouse cursor. FIXED-IN:5.27 M +18 -2 kcm/kcm.cpp M +7 -1 kcm/kcm.h M +7 -2 kcm/package/contents/ui/main.qml https://invent.kde.org/plasma/kscreen/commit/f95cbe13d347f74a8b53f0ff2a6e28def8e8529f Git commit 69544dc72bc0bfa8ebb0b50c542eea1d763af7fd by David Redondo. Committed on 21/11/2022 at 09:49. Pushed by davidre into branch 'master'. kcm: In the case of two outputs always snap them together While being a harder problem in general, when there are only two outputs we can make them always touch which is better than showing a warning after the move. M +60 -5 kcm/output_model.cpp https://invent.kde.org/plasma/kscreen/commit/69544dc72bc0bfa8ebb0b50c542eea1d763af7fd |