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: Paul Maier <svn-user@web.de>, dickey@his.com
Subject: Re: AW: AW: AW: Can't paste text or type blind keys when mouse is out of the window
Date: Wed, 05 Oct 2011 13:03:00 -0000	[thread overview]
Message-ID: <4E8C556E.7020607@dronecode.org.uk> (raw)
In-Reply-To: <000001cc82f8$f64689e0$e2d39da0$@de>

On 05/10/2011 01:51, Paul Maier wrote:
>>>>>> I assume that you see the same behavior with other X applications, i.e. it's
>>>>>> not xterm-specific?
>>>>>
>>>>> No, at least xedit works fine on my PC, with blind keys and with mouse text pasting,
>>>>> no matter if the mouse pointer is really inside or on blue window frame or
>>>>> (for blind keys:) really outside.
>>>>
>>>> Actually, maybe this is an xterm problem?
>>>>
>>>> It seems to be somehow related to the xterm's --enable-toolbar configuration
>>>> (which is turned on in the cygwin package).  If I rebuild xterm with that
>>>> disabled, the problem goes away, and I can also reproduce the problem on F15
>>>> under twm if I build xterm with --enable-toolbar there (which is not enabled
>>>> in the distro supplied package)
>>
>> hmm - I'm not clear on precisely what a "blind key" is.  Sounds like a
>> compose sequence - and if so, it's puzzling that passing key-presses from
>> different levels in the widget hierarchy would interfere with that.
>>
>> The main difference with the toolbar configuration is that xterm's using a
>> form to contain the toolbar and the vt100 window.  The buttons take care
>> of themselves, but that area to the right of the buttons is dead.
>>
>> To make it somewhat friendlier, xterm adds the actions used for the vt100
>> window (except for the ones related to the mouse) to the toolbar area.
>>
>> I omitted the mouse-related ones since it seems that they'd interfere with
>> the menus.  I also did the same for the scrollbar widget (since keystrokes
>> there used to be lost - it would seem that you could reproduce your
>> problem also by looking at the behaviour around the scrollbar).
>
>
> yes, with mouse over the scrollbar the problem is reproducable.
>
> A blind key is a key that needs to be followed by another key to produce something.

I think this is usually called a 'dead key'

-- 
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:[~2011-10-05 13:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07  9:06 Paul Maier
2011-09-07 12:25 ` Jon TURNEY
2011-09-08 20:53   ` AW: " Paul Maier
2011-09-09 11:42     ` Jon TURNEY
2011-10-03 10:37       ` AW: " Paul Maier
2011-10-04  0:35         ` Thomas Dickey
2011-10-05  0:54           ` AW: " Paul Maier
2011-10-05  1:00             ` Thomas Dickey
2011-10-30 23:04               ` AW: " Paul Maier
2011-10-31  3:33                 ` Thomas Dickey
2012-07-22  0:28                   ` AW: AW: AW: AW: AW: Can't paste text or type dead " Paul Maier
2012-07-23  9:01                     ` Thomas Dickey
2011-10-05 13:03             ` 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=4E8C556E.7020607@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=dickey@his.com \
    --cc=svn-user@web.de \
    /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).