From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Issue with inserting '@' at the command prompt.
Date: Fri, 19 Aug 2011 13:51:00 -0000 [thread overview]
Message-ID: <20110819135020.GA6794@calimero.vinschen.de> (raw)
In-Reply-To: <20110819131459.GO4919@type.famille.thibault.fr>
On Aug 19 15:14, Samuel Thibault wrote:
> Corinna Vinschen, le Fri 19 Aug 2011 13:50:19 +0200, a écrit :
> > > .wVirtualKeyCode = 0x630,
>
> Eergl, no, that should have been 0x30 here, our code does properly masks
> out the high part, I just missed that in our code.
And what about the control code? It's a fixed 1 in your example, but
obviously it should be 6.
> > a simple testcase (wow!)
>
> Sorry, but I'm not paid for this, I don't actually use the software at
> all (neither brltty nor windows), don't actually own the hardware (thus
> had to emulate it in qemu by first reverse-engineering the actual device
> behavior),
Same here. I tested this on a Qemu/KVM driven W7 box.
> it just seems I'm the only guy in the world that knows a bit
> about both brltty and windows and knows that some people *need* it, and
> I thus spend time on it, and it was already almost 5am...
>
> > /* Create correct CtrlKeyState from high byte returned by VkKeyScanW. */
> > if (vks & 0x100)
> > ctrl |= SHIFT_PRESSED;
> > if (vks & 0x200)
> > ctrl |= RIGHT_CTRL_PRESSED;
> > if (vks & 0x400)
> > ctrl |= RIGHT_ALT_PRESSED;
>
> Err, do you mean LEFT_ALT_PRESSED here? Right alt is altgr in some
> keyboard layouts, which is precisely what people use to type '@' in
> the french layout, actually. E.g. LeftAlt-A and RightAlt-A (i.e.
I'm aware of this difference, so, no, that was a deliberate
RIGHT_ALT_PRESSED. However, this also works for me when using
LEFT_CTRL_PRESSED and LEFT_ALT_PRESSED in the conditionals above.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-08-19 13:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 11:42 [Lars Bjørndal] Re: brltty problems with recent snapshots Lars Bjørndal
2011-07-13 12:35 ` Lars Bjørndal
2011-07-13 13:07 ` Corinna Vinschen
2011-07-13 15:37 ` Christopher Faylor
2011-07-13 13:06 ` [Lars Bjørndal] " Corinna Vinschen
2011-07-13 13:37 ` Samuel Thibault
2011-07-13 19:01 ` Corinna Vinschen
2011-07-13 19:25 ` Lars Bjørndal
2011-07-13 20:00 ` Corinna Vinschen
2011-07-14 8:20 ` Lars Bjørndal
2011-07-14 10:16 ` Corinna Vinschen
2011-07-14 10:56 ` Lars Bjørndal
2011-07-14 12:42 ` Samuel Thibault
2011-08-19 2:38 ` Issue with inserting '@' at the command prompt Samuel Thibault
2011-08-19 2:45 ` Samuel Thibault
2011-08-19 11:50 ` Corinna Vinschen
2011-08-19 13:15 ` Samuel Thibault
2011-08-19 13:51 ` Corinna Vinschen [this message]
2011-08-19 14:07 ` Samuel Thibault
2011-08-19 15:09 ` Corinna Vinschen
2011-08-19 15:16 ` Samuel Thibault
2011-08-19 15:33 ` Corinna Vinschen
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=20110819135020.GA6794@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@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).