>> 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).
> Yes, centered at this location. But when close to an edge, a part of the
> window can be displayed outside. This case was handled in a
> big-rectangle-screen fashion, but not when all monitors do not have the
> same size. Now it is OK. Note that same policy applies when displaying a
> menu and for f.identify window.
Ah, yes. Nice.
>> 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.> [snip]
>
> That describes pretty well the problems I encountered :)
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.
Stefan
