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: raul@cantara.com Subject: Re: Problems with display resize over RDP connections Date: Sun, 18 Jul 2010 15:45:00 -0000 [thread overview] Message-ID: <4C43219C.5010104@dronecode.org.uk> (raw) In-Reply-To: <535CCD22-D909-4FEA-B5A0-7DCA4B4079CE@cantara.com> On 29/04/2010 03:49, Raul Acevedo wrote: > Didn't X figure out how to dynamically change its display resolution long > time ago? (I remember the "good old days" when this really was fixed on > server start up, and the only way to change it was to restart X.) Isn't > there some way to tell the X server, even if it's via a command line > utility, that the display has been reconfigured? Modern Linux desktops > certainly let me do this. It's true that X can handle display resolution changes with the RANDR extension, but support needs to be present in the DDX layer as well, and currently the XWin DDX doesn't have this. I've been working on some changes to add this support, which seem to work ok and could use some wider testing. * Add RANDR extension support to XWin DDX. * In multiwindow or rootless mode handle the WM_DISPLAYCHANGE message sent when monitor resolution or number changes. Use RANDR to update the X screen size to the virtual desktop size (if -multiplemonitors was used) or to the monitor size (if -screen @monitor was used) * In rooted mode, a new option -resize is added to control resizing mode. When -resize=randr mode is selected, the native window containing the root window has a resizing frame and resizing the frame will use RANDR to change the size of the X screen. Likewise, RANDR changes of X screen size will update the size of the native window containing the root window. I've uploaded a build including these changes at [1]. Perhaps you could try it out and see if it works for you? Patches are rather large so they can be found at [2] [1] ftp://cygwin.com/pub/cygwinx/XWin.20100718-git-c8262c6457efa195.exe.bz2 [2] http://cgit.freedesktop.org/~jturney/xserver/log/?h=jturney-framebuffer-resize > This is definitely over a secure link. I'm not 100% sure what protocol is > used; I go through a web portal interface, so it's not like I'm running a > VNC/RDP client directly. > > Thanks, > > Raul > > On Apr 28, 2010, at 7:16 PM, Jim Reisert AD1C wrote: > >> 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. This is mentioned in the XWin manpage as a bug. -- 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/
prev parent reply other threads:[~2010-07-18 15:45 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 2010-04-29 12:17 ` Raul Acevedo 2010-07-18 15:45 ` 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=4C43219C.5010104@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=raul@cantara.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: linkBe 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).