public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jack Tanner <ihok@hotmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Configuration for multiple monitors
Date: Fri, 09 Jan 2004 18:59:00 -0000	[thread overview]
Message-ID: <btmtms$q13$1@sea.gmane.org> (raw)
In-Reply-To: <1073640179.8704.4.camel@famine>

Øyvind Harboe wrote:
> perhaps the below should *always* be TRUE and there shouldn't be 
> an option at all?

No, I'd like -nomultiplemonitors to exist.

I have two monitors, but the second is usually turned off. Various X 
client dialog boxes and application windows usually come up in the 
center of my desktop, which means half on one monitor, and half on the 
other. If that weren't annoying enough, it makes life sheer hell when 
one monitor is turned off!

This is why I do not use -multiplemonitors, even though I /have/ 
multiple monitors. Even when both monitors are turned on, it's plenty to 
have one for X apps, and another for regular Windows apps.

Granted, the real solution to this issue would be to play nice with 
nVidia's nView software. It offers these modes for dual-monitor work 
(the following is copied verbatim from nView on-line help; the mode I 
use is Dualview, which I believe is nVidia's default):

Single Display. Only one of your connected displays is used.

Clone. Both displays in the display pair show images of the same desktop.

Horizontal Span. Both displays in the display pair behave as one wide 
virtual desktop. The width of each display is half the width of the 
total virtual desktop width.

Vertical Span. Both displays in the display pair behave as one tall 
virtual desktop. The height of each display is half the heiht of the 
total virtual desktop height.

Dualview. Both displays in the display pair behave as one virtual 
desktop. Unlike Horizontal or Vertical Spanning mode, Dualview treats 
ach display as a separate device. This means that the task bar will not 
be stretched across displays and 3D applications are not accelerated as 
efficiently if the application Spans displays.

-JT



  reply	other threads:[~2004-01-09 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09  9:23 Øyvind Harboe
2004-01-09 18:59 ` Jack Tanner [this message]
2004-01-10 16:34   ` Harold L Hunt II
2004-01-10 16:38 ` Harold L Hunt II
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 17:47 Øyvind Harboe
2004-01-08 18:12 ` Harold L Hunt II

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='btmtms$q13$1@sea.gmane.org' \
    --to=ihok@hotmail.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).