public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: jbdean@gmail.com
Subject: Re: empty x windows
Date: Sun, 18 Jul 2010 15:04:00 -0000	[thread overview]
Message-ID: <4C431804.5070508@dronecode.org.uk> (raw)
In-Reply-To: <4C168507.6010803@gmail.com>

On 14/06/2010 20:37, J. Bruce Dean wrote:
> When running dual displays, using cygwin/x, the external monitor frames are
> 'invisible'. The window moves from the (laptop) display, working, on the
> external monitor they have a border, but the background is a snapshot of
> the app running on the external monitor. If I type, it works, but nothing
> displays. Moving the window moves the snapshot of the background. Moving
> back to the primary display I can see whatever I typed on the external
> monitor. Searching provided some things to try, such as the 'screens' and
> 'mulitplemonitors', neither worked.

Another other thing I've recently come across which might cause this behaviour 
is if the 2 monitors have different colour depths.  In that case, something 
does get written to XWin.0.log indicating that we will use the primary display 
only (effectively turning off -multiplemonitors), but I guess it could be clearer.

Perhaps we should arrange to constrain the X windows to stay in the area of 
the virtual desktop for which the shadow framebuffer covers, to avoid windows 
which don't get their contents drawn like that.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


      parent reply	other threads:[~2010-07-18 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 19:37 J. Bruce Dean
2010-06-14 19:47 ` Jeff Spirko
2010-07-18 15:04 ` Jon TURNEY [this message]

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=4C431804.5070508@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=jbdean@gmail.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).