Hi, Le 28/03/2018 à 17:21, Stefan Monnier a écrit : > Hi, > > I'm trying your `master` branch right now (not sure what's the > difference with your `xrandr` branch), thanks (I have a dual-head setup > with two 1200x1600 monitors side by side to get a 2400x1600 area).
All my work is now in master branch, xrandr is not updated anymore. With your 2 same-size-monitors you are in a situation where ctwm works well without the XrandR feature, as your total-screen is a rectangle. You will gain the monitor edge detection in case you use pack moves or want to zoom on only one monitor. > >> * f.occupy window now uses layout (to stay visible); > > Not sure what this means. f.occupy displays a window. In case the screen is not rectangular, this makes the window always visible even when it could appear (even partially) in a hidden zone... +-------+-----+ | mon1 | mon | +-------+ 2 | hidden | | zone +-----+ > >> * If CenterFeedbackWindow, feedback window is centered in first monitor; > > I didn't really like the way the feedback was straddling my two > monitors, so this is better, but I think that instead of always using > the first monitor it would make sense to use the center of the "current" > monitor, so when I'm resizing a window in the second monitor I don't > have to look at the first monitor to see what's the size. Done in last commit. > >> Does anyone really use VirtualScreens? > > I'm not using it right now, but I've used it in the past and I liked it. You're lucky, I have never succeeded to use it without any problem... > To be honest, I thought/hoped your patch would automatically treat > each monitor kind of like a VirtualScreen. > > At least having it as an option would be great. > [snip] As VirtualScreens did not work for me, I am not right man to make it work in a new environment... ++ Max.
