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
Subject: Re: screen not updated outside 1680x1050
Date: Wed, 03 Feb 2010 19:43:00 -0000	[thread overview]
Message-ID: <4B69D1FF.2070107@dronecode.org.uk> (raw)
In-Reply-To: <a9a39a210912172211p2861948fu2c921c84e35e0260@mail.gmail.com>

On 18/12/2009 06:11, Frédéric Bron wrote:
>>> XWin -multiwindow -clipboard -silent-dup-error
>>>
>>> ddxProcessArgument - Initializing default screens
>>> winInitializeDefaultScreens - w 1680 h 1050
>>                                 ^^^^^^^^^^^^^
>> Looks like the system doesn't see your whole resolution at startup.
>> I'd pass "-screen 0 1920x1200" to XWin.exe.  I tried this to reduce my screen resolution,
>> and saw things similar to what you describe outside the declared screensize.
>
> Works fine, thanks a lot! In fact I saw only the following lines so
> that I thought it was OK with the resolution:
>
> 2009-12-17 13:47:46 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32,
> last bpp: 32, new bpp: 32
> 2009-12-17 13:47:46 winWindowProc - WM_DISPLAYCHANGE - new width: 1920
> new height: 1200

As you have discovered, XWin doesn't understand about display resolution 
changes.  This is actually mentioned in the XWin man page, and at [1]

[1] http://x.cygwin.com/devel/todo.html

--
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/


      reply	other threads:[~2010-02-03 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 22:47 Frédéric Bron
2009-12-18  0:03 ` Mike Ayers
2009-12-18  6:11   ` Frédéric Bron
2010-02-03 19:43     ` 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=4B69D1FF.2070107@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).