>> 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.
Ah, OK, good.
> 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.
Yes, it worked OK, but when do "horiz-zoom" more often than not I don't
want a 2400-wide xterm but only a 1200-wide one.
> You will gain the monitor edge detection in case you use pack moves or
> want to zoom on only one monitor.
Yes I like the edge detection as well (I have a vague recollection that
I contributed some of the original edge detection, way back when).
>>> * 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 +-----+
Ah, I see. I thought that it used to be displayed at the location of
the affected window (tho a quick test seems to show it's actually
placed wherever the mouse was when the action was triggered).
>>> * 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.
Thanks (will test it when I get to enjoy my two-monitor setup).
>>> 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...
It's been a while since I managed to use it. I liked the ability to
switch workspaces separately.
I tried it with a manual
VirtualScreens {
"1200x1600+0+0"
"1200x1600+1200+0"
}
and it seemed to be somewhat working. For some reason it seems like it
doesn't "bring in" the previously existing windows (at least I couldn't
see them, I had to remove the VirtualScreens declaration and restart
ctwm to recover my windows). And clicking in the background of the
second monitor brought up the menu in the first monitor :-(
I'm sure there are many more quirks.
Stefan
