Bug 348241 - Option to not snap displays to each other
Summary: Option to not snap displays to each other
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (show other bugs)
Version: 5.14.3
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
: 393873 441486 472256 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-05-26 11:52 UTC by Soukyuu
Modified: 2023-09-11 22:23 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Soukyuu 2015-05-26 11:52:08 UTC
I'm trying to reposition my second monitor, but kscreen won't let me do it the way I want it to.
Namely, I can't get a vertical offset of ~60px because anything < 140px makes the second monitor snap to 0 on the Y-axis.

Is there a way to disable snapping? If not, can it please be added?

Reproducible: Always

Steps to Reproduce:
1. Move a second monitor down vertically
2. Attempt to get an offset <140px

Actual Results:  
The second monitor snaps to the first, aligning the horizontal edges.

Expected Results:  
Ability to finetune the position without the snapping feature interfering

I see several possible approaches:
- have cursor keys move the currently selected monitor by 1px (and a text hint stating it's possible)
- two edit fields that hold the current offsets for the selected monitor, so it's editable by hand
- a checkbox to toggle snapping

For now I just edit the configuration file in /$HOME/.local/share/kscreen as a workaround, but this effectively stops me from using the kcm module to manage any additional screens because i will have to edit the config file afterwards anyway.
Comment 1 Daniel Vrátil 2015-06-04 12:36:22 UTC
It used to be possible to disable snapping by holding Ctrl while dragging the output around, but looks like it got lost when porting to KF5, so yep, this should definitely be brought back.
Comment 2 Christoph Feck 2018-05-31 23:32:55 UTC
*** Bug 393873 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2022-11-10 22:05:07 UTC
Allowing the exact pixels values to be manipulates is tracked with Bug 355119.
Comment 4 Nate Graham 2022-11-12 14:20:20 UTC
*** Bug 441486 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2023-09-11 22:23:26 UTC
*** Bug 472256 has been marked as a duplicate of this bug. ***