Keith Nash <
[email protected]> wrote:
A new toplevel can be created on any available screen by using the
option -screen, e.g.
toplevel .foo -screen :1.0
Screens are an old concept from X11, where two monitors attached
to a single machine (usually via separate graphics-boards, as each
board usually only had a single port) and handled by the same
Xserver were handled separately as :0.0 and :0.1 (that was back
in last millennium)
Then, later (I think still last millennium) came (optional) Xinerama,
where these :0.0 and :0.1 were united to a single big screen, where
you could even have single windows extending across the monitor-
boundaries. Quite a "wow!" back then.
Nowadays, graphics-boards have multiple ports, and multiple
graphics-boards are usually treated together as some dynamic
screen-estate, which just grows or shrinks as further monitors
get connected or disconnected, or the laptop-lid opened or closed.
Since the time I have more than one monitor plugged to my machine
(like about 10 years now), I haven't seen any :0.1 anymore, but just
a single screen extending to all of them, and tools (e.g. arandr
or those monitor-settings dialogs) to arrange their relative layout
or switch to "mirroring" the same screen to all monitors.
Given that monitors can be put in quite peculiar relative layouts,
e.g. touching only in corners rather than along edges, it is probably
quite non-trivial to identify a specific monitor and the rectangle of
virtual big screen that it displays, at least for a simple application,
unless it assumes running locally and being able to ask system utilities
like xrandr for such information (on linux, no idea if windows has a
pendant). These things would fail, if running remotely - e.g. over an
ssh X-forwarding tunnel.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)