public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Simon Marlow <marlowsd@gmail.com>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: XCygwin <cygwin-xfree@cygwin.com>
Subject: Re: Slow response to keypresses in xorg-server-1.8.0-1
Date: Mon, 19 Jul 2010 15:45:00 -0000	[thread overview]
Message-ID: <4C447321.3010401@gmail.com> (raw)
In-Reply-To: <4C44668C.9030102@alice.it>

On 19/07/2010 15:51, Angelo Graziosi wrote:
> Simon Marlow wrote:
>
>> I use the VirtuaWin virtual-desktop tool, and found that often when
>> switching to a desktop with XWin windows on it, the windows would
>> remain blank until I right-clicked on the XWin icon in the tray, when
>> they would refresh.
>
> Strange. It is more than an year I use VirtuaWin (now 4.2) without
> problems with X, and I use the not-patched XWin.exe, i.e. that from
> original 1.8.0-1 package.
>
> Perhaps you have a BLODA[*]?

I have MS Forefront client security, configured to omit the Cygwin 
directories, but I really doubt that's the problem.

More details about what I do to reproduce the not-refreshing problem 
(not the blank window problem, that seems to be fixed by the patched 
XWin binary, and judging by other comments in this thread seems to be a 
known issue unrelated to VirtuaWin).

  - multiple xterms running on remote machines displaying locally,
    over multiple 'ssh -Y' connections, i.e. I do
       ssh -Y remote-machine xterm

  - windows are on adjacent desktops, using overlapping areas of the
    screen

  - switch between the desktops, note how the windows on the new
    desktop are still displaying the content of the windows on the
    previous desktop.  Alas, it doesn't always happen, but it
    happens a lot.

In VirtuaWin I have "Static taskbar & Z order" set for "On desktop 
change preserve".  I did try using different hiding methods for XWin 
windows in VirtuaWin, but didn't find anything that worked.

Cheers,
	Simon

--
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-07-19 15:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 14:52 Angelo Graziosi
2010-07-19 15:45 ` Simon Marlow [this message]
2010-07-19 23:01   ` Angelo Graziosi
2010-07-20  8:07     ` Simon Marlow
2010-07-20  8:43       ` Angelo Graziosi
  -- strict thread matches above, loose matches on Subject: below --
2010-07-01 20:49 Leigh Orf
2010-07-01 21:24 ` Larry Hall (Cygwin X)
2010-06-29 20:40 Robert Daasch
2010-06-10 16:42 Joseph Ess
2010-06-02 16:52 Tony Hammitt
2010-05-20 23:26 J. Offerman
2010-05-01 13:49 Ken Brown
2010-05-02 20:52 ` Ken Brown
2010-06-30 17:40   ` Jon TURNEY
2010-07-01  2:02     ` Ken Brown
2010-07-01 21:07     ` Marco Atzeri
2010-07-19 14:11     ` Simon Marlow
2010-08-05 18:53     ` Laurent Montaron
2010-08-07 15:39       ` Reini Urban
2010-08-07 22:07         ` Jon TURNEY
2010-08-08 11:05           ` Andy Koppe

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=4C447321.3010401@gmail.com \
    --to=marlowsd@gmail.com \
    --cc=angelo.graziosi@alice.it \
    --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).