>> Could add an option to automatically provide the VirtualScreens thingy
>> based on the xrandr monitor information?
>> It wouldn't fix those quirks, clearly, but it might encourage people to
>> use VirtualScreens and in turn to try and fix them.
> If we want to go this way, we have to define clearly what VirtualScreens
> should provide.
I was thinking of having a new option such as
VirtualScreensViaXRandR
which would behave as if you had written a VirtualScreens { ... }
section with one virtual screen per monitor.
> At this time, sharing the same config file for different
> size screens is for example de facto problematic (workspace manager
> position and other geometry settings).
I think you're referring to yet-another-problem with VirtualScreens.
I agree that there are probably lots of problems to solve there, but
that seems independent from the introduction of VirtualScreensViaXRandR.
> Moreover, the actual implementation of this feature really complicates
> the code.
Which feature? VirtualScreens? or VirtualScreensViaXRandR?
Stefan
