public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Problems with display resize over RDP connections
Date: Thu, 29 Apr 2010 02:50:00 -0000 [thread overview]
Message-ID: <4BD8EBFA.2040503@alum.mit.edu> (raw)
In-Reply-To: <8565D35C-3708-4A1B-B5A2-698A308F3454@cantara.com>
My understanding is that the X server inherits the properties of the
screen it's started on. For example, if you normally have 2 monitors,
and for some reason only 1 monitor is active, and you start Xwin there,
if you then active the 2nd monitor, you can't move your Xterm window
over there (or you can, but you can't do anything with it).
What is RDP? I like LogMeIn for this sort of thing, as long as you're
not on a secure (ie. VPN) connection. I really HATE when you log into a
remote system and it changes those screen properties. Then when you come
into work, it's all messed up.
On 4/28/2010 12:38 PM, Raul Acevedo wrote:
> At work, my display is at 1280x1024. When I RDP from home, I have a
> bigger screen so my work computer's desktop is resized to 1920x1200. When
> this happens, X applications cannot display anything below 1024 pixels;
> below 1024 pixels nothing is displayed, and you can see the other
> application windows underneath the current X window below 1024 pixels.
>
> Is this a known issue? It's a pain to restart X and my apps just to get
> X to properly adjust its display size.
>
> Thanks,
>
> Raul Acevedo
> http://www.cantara.com
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
--
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/
next prev parent reply other threads:[~2010-04-29 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 2:16 Raul Acevedo
2010-04-29 2:50 ` Jim Reisert AD1C [this message]
2010-04-29 12:17 ` Raul Acevedo
2010-07-18 15:45 ` Jon TURNEY
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=4BD8EBFA.2040503@alum.mit.edu \
--to=jjreisert@alum.mit.edu \
--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).