From: "Zeng, Star" <star.zeng@intel.com>
To: Heyi Guo <heyi.guo@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"Dong, Eric" <eric.dong@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: [MdeModulePkg/TerminalDxe] Why do we delay 2s for ESC being pressed?
Date: Wed, 8 Nov 2017 07:24:59 +0000 [thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103B9B3162@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1958e840-f0fe-6d8e-44d1-03ff9c9dde7b@linaro.org>
Cc Terminal expert Ray to see if any comments on this.
Thanks,
Star
-----Original Message-----
From: Heyi Guo [mailto:heyi.guo@linaro.org]
Sent: Wednesday, November 8, 2017 3:04 PM
To: edk2-devel@lists.01.org
Cc: Zeng, Star <star.zeng@intel.com>; Dong, Eric <eric.dong@intel.com>
Subject: [MdeModulePkg/TerminalDxe] Why do we delay 2s for ESC being pressed?
Hi folks,
We found ESC key responded fairly slow on serial port terminal, and we think it might be caused by the code in UnicodeToEfiKey in TerminalConIn.c:
if (UnicodeChar == ESC) {
TerminalDevice->InputState = INPUT_STATE_ESC;
}
if (UnicodeChar == CSI) {
TerminalDevice->InputState = INPUT_STATE_CSI;
}
if (TerminalDevice->InputState != INPUT_STATE_DEFAULT) {
Status = gBS->SetTimer(
TerminalDevice->TwoSecondTimeOut,
TimerRelative,
(UINT64)20000000
);
ASSERT_EFI_ERROR (Status);
continue;
}
It seems we intentionally add 2 seconds delay for ESC key press. This provides not so good user experience when we press ESC to exit or cancel some operation.
We tried reducing this timeout value to 1 second, then the experience improved much and we didn't find any issue introduced.
What's the reason for this timeout value and is there any improvement?
Thanks and regards,
Heyi
next prev parent reply other threads:[~2017-11-08 7:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 7:04 [MdeModulePkg/TerminalDxe] Why do we delay 2s for ESC being pressed? Heyi Guo
2017-11-08 7:24 ` Zeng, Star [this message]
2017-11-08 7:55 ` Ni, Ruiyu
2017-11-08 8:30 ` Heyi Guo
2017-11-08 8:34 ` Ni, Ruiyu
2017-11-08 8:44 ` Heyi Guo
2017-11-08 8:46 ` Ni, Ruiyu
2017-11-08 8:51 ` Heyi Guo
2017-11-08 9:07 ` Gerd Hoffmann
2017-11-08 13:34 ` Heyi Guo
2017-11-08 16:00 ` Brian J. Johnson
2017-11-24 7:21 ` Heyi Guo
2017-11-28 17:55 ` Brian J. Johnson
2017-11-29 4:18 ` Andrew Fish
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-list 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=0C09AFA07DD0434D9E2A0C6AEB0483103B9B3162@shsmsx102.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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