https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #14 from Andrea ---
@Martin, the argument "I am not payed to do this and I don't want to, so stop
bothering me" is, at last, a very convincing one :)
Much more convicing than "we know what's good for the users stop complaining
and be happy
https://bugs.kde.org/show_bug.cgi?id=346795
Martin Gräßlin changed:
What|Removed |Added
CC|mgraess...@kde.org |
--- Comment #13 from Martin Gräßlin ---
> @M
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #12 from Andrea ---
@Martin because other DE do not have this problem. If this were really
something inherently missing upstream and impossible to solve, as you say,
everybody would have the same problem.
So, setting aside the discussions o
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #11 from Martin Gräßlin ---
@Andrea: why do you insist that we should do something about it? You even agree
that us guessing is not optimal? Why are you asking us for writing code which
will break, which will be broken while the code could b
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #10 from Andrea ---
Hi Martin, thanks for the explanation, I finally understand the problem, and I
agree that having kde guessing is not optimal.
Still, in the case we are discussing here, there is a configuration with one
output screen and
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #9 from Martin Gräßlin ---
> Once the relative position of the multiple monitors is set, it seems to me
> all the offsets are also fully known.
It's not that simple obviously. I spent quite some thinking about the issue
since March when I
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #8 from Andrea ---
Thanks for the clarifications, but there is still something I just don't
understand. You say kde has not enough information to solve the issue, but
isn't all you need already available in the "Display and Monitor" panel in
https://bugs.kde.org/show_bug.cgi?id=346795
Martin Gräßlin changed:
What|Removed |Added
CC||mgraess...@kde.org
--- Comment #7 from Martin
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #6 from jan...@hbz-nrw.de ---
To be honest: I don´t know anything about the systems architecture and the
dependencies between KDE components and X. And generally KDE developers seem to
know what they´re doing - otherwise KDE wouldn´t probably
https://bugs.kde.org/show_bug.cgi?id=346795
Sebastian Kügler changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #4 from Sebastian Kügler ---
Martin Gräßlin has added a note to look into this, so it doesn't get forgotten.
We'll leave it under KScreen for now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=346795
--- Comment #3 from Sebastian Kügler ---
We've discussed this, and it's not libkscreen's business (kscreen is about
monitors / screens, not about input devices).
This is probably an upstream bug, either in Xorg or in libinput, and if
libinput isn't cur
https://bugs.kde.org/show_bug.cgi?id=346795
Kai Uwe Broulik changed:
What|Removed |Added
Assignee|aleix...@kde.org|se...@kde.org
Component|Multi-screen
13 matches
Mail list logo
