On Sun, 25 Nov 2018 04:47:39 -0700 Roman Gilg wrote
> From a user-facing standpoint there is not much change. Certain
> display property a user manipulates manually via the KCM are now per
> default persistent over all possible configurations of displays (i.e.
> which displays
On Sat, Nov 24, 2018 at 8:42 PM Nate Graham wrote:
> [CCing visual-des...@kde.org]
>
> Hi Roman,
> Could you summarize for less technical people like me what the
> user-facing impact of this change would be? How would this change the
> experience of managing external screens for laptop users? Etc.
On November 24, 2018 at 12:43:00 PM, Nate Graham (n...@kde.org) wrote:
> [CCing visual-des...@kde.org]
>
> Hi Roman,
> Could you summarize for less technical people like me what the
> user-facing impact of this change would be? How would this change the
> experience of managing external screens
[CCing visual-des...@kde.org]
Hi Roman,
Could you summarize for less technical people like me what the
user-facing impact of this change would be? How would this change the
experience of managing external screens for laptop users? Etc.
Nate
On 11/19/18 3:11 AM, Roman Gilg wrote:
Hi all,
On Mon, Nov 19, 2018 at 11:56 AM David Edmundson
wrote:
>
> The concept of the global values makes sense. But I think you've over
> complicated it.
>
> I don't think we should retroactively apply global changes to setups.
> The UX is super confusing, and we have all these state problems that requ
On Mon, Nov 19, 2018 at 3:00 PM Christoph Feck wrote:
>
> On 19.11.2018 11:11, Roman Gilg wrote:
> > D1 is at coordinates (0, 0) and has logical size 3840x2160. D2 is
> > therefore at coordinates (3841, 0).
>
> Is the single-pixel gap intended, or should that read (3840, 0)?
>
It should be indeed
On 19.11.2018 11:11, Roman Gilg wrote:
D1 is at coordinates (0, 0) and has logical size 3840x2160. D2 is
therefore at coordinates (3841, 0).
Is the single-pixel gap intended, or should that read (3840, 0)?
The concept of the global values makes sense. But I think you've over
complicated it.
I don't think we should retroactively apply global changes to setups.
The UX is super confusing, and we have all these state problems that
require more and more code on top.
All I think is needed is:
- we save
Hi all,
I've written over the last few days a patch series for KScreen, that
restructures part of the code, but more importantly introduces new
configuration concepts on a fundamental level.
I write this mail to get some feedback on these concepts, if there are
aspects I overlooked when designing
