From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-developers@cygwin.com
Subject: Re: read vs select on mouse events in console
Date: Sat, 24 Dec 2022 20:37:29 +0900 [thread overview]
Message-ID: <20221224203729.9ed9a7280f1318bf9c4ce774@nifty.ne.jp> (raw)
In-Reply-To: <eb2f03ca-170f-e478-dfc1-16e7548cc01a@towo.net>
On Fri, 23 Dec 2022 13:03:06 +0100
Thomas Wolff wrote:
> Am 23.12.2022 um 11:19 schrieb Takashi Yano:
> > On Fri, 23 Dec 2022 10:08:20 +0100
> > Thomas Wolff wrote:
> >> I see different behavior indeed; no further output of (0) and Windows
> >> display its message to make a mouse selection in the title bar.
> > Ah, that may be due to "Quick Edit Mode". It seems that the
> > "Quick Edit Mode" is disabled in the DECSET 1000 range, however,
> > it is enabled outside of the range. So, clicking mouse outside of
> > the range triggers the "Quick Edit Mode" then program is suspended.
> >
> > If you uncheck the "Quick Edit Mode" setting, the problem will probably disappear. Please try.
> Right, but how does Windows notice about mouse events processed by
> cygwin, so it enters quick edit mode or not?
> Still mysterious.
Actually, mouse_aware() is not used after Win10 1703.
Mouse event is translated to ESC sequence by Windows.
ENABLE_VIRTUAL_TERMINAL_INPUT flag does that. Therefore,
Windows knows whther the mouse event is processed or not.
mouse_aware() works only if the system is before win10
1607 or legacy console mode is enabled.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2022-12-24 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 14:55 Thomas Wolff
2022-12-23 3:24 ` Takashi Yano
2022-12-23 9:08 ` Thomas Wolff
2022-12-23 10:19 ` Takashi Yano
2022-12-23 12:03 ` Thomas Wolff
2022-12-24 11:37 ` Takashi Yano [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=20221224203729.9ed9a7280f1318bf9c4ce774@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-developers@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).