Re: Multiple monitors, VirtualScreens and/or Xrandr

Le 03/04/2018 à 15:55, Stefan Monnier a écrit :
>> - ability for a window to be in several workspaces (as it is already
>> possible), but at different positions (add a functions family to zoom/move
>> on current workspace only + reset position);
>> - possibility to tag windows (a window could have one or several tags) and
>> have commands to operates on these tags (move, iconify, workspace
>> occupation) ?
> 
> Sound potentially useful, but I'm not sure what a good UI for that would
> look like.

The only UIs needed is a menu of known tags + possibility to add new
ones (something as simple as the workspace rename feature might be enough.)

> 
>> This way you could compose each workspace as you want, without being
>> constrained by screens sizes and this VirtualScreens layer.  What do you
>> think about that?
> 
> Maybe for VirtualScreens to work when the virtual screens don't all have
> the same size, we should simply start by making those even more like
> separate displays: each virtualscreen would get its own set
> of workspaces.
> 
> Currently if you have (say) 6 workspaces in your ctwm config, then those
> 6 are shared between the two virtual screens which creates problem if
> you setup a workspace on screen 0 and then select it in screen 1 since
> the two screens may have different sizes.  It also creates the problem
> of what to do when different screen want to display the same workspace
> at the same time.
> 
> Splitting them into 12 workspaces (6 per screen) would solve this in
> a very straightforward manner.
> 
> Along the same lines, a window that's in screen 0 could only belong to
> workspaces of screen 0 and not to workspaces of other screens (so
> there's never a situation where you might need to display a given window
> at two different places at the same time).  Of course, displaying
> a given window at several places at the same time might be reasonably
> easy to do by "compositing" but I don't know if anyone is up to making
> ctwm do it.

It would complicates the code a level more.

We can not dissociate screens as you describe without facing problems.
As if a window has its left part on first screen and its right one on
the second screen, what should happen ?

No, I think it is the wrong way to try to handle N X11-joined screens as
N independent screens.

++

Max.