mirror of
https://github.com/rivo/tview.git
synced 2026-04-26 13:25:51 +03:00
[GH-ISSUE #597] app.Stop() and app.Suspend() require an additional keypress before clearing screen #437
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tview#437
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lukegalea on GitHub (May 6, 2021).
Original GitHub issue: https://github.com/rivo/tview/issues/597
Both when using app.Stop() to exit a tview application, or when using app.Suspend(), I'm finding that a second keypress is required before the user actually "sees" the app stop.
in the trivial example below, a single press of escape should exit the program... but instead, the first press of escape doesn't clear the screen nor exit the program.. but a second keypress of any kind (enter, a second escape.. whatever) does trigger the program closing and the screen clearing.
I've tried seeding the program w/ debug output (fmt.Println) to confirm that app.Stop is being called.. and it is.. it just doesn't have the desired effect.
@lukegalea commented on GitHub (May 6, 2021):
A colleague has confirmed for me that this is not a problem on OSX. A single press of escape clears the screen and exits the process.,
I've confirmed it to be a problem on multiple linux distros, though.
@mdom commented on GitHub (May 10, 2021):
This bug does also effect OpenBSD 6.8. I'm just running the hello world demo from the README page in a xterm and i need to type another key after Ctrl-C for the application to quit.
@D54 commented on GitHub (May 10, 2021):
It also affects Linux.
Tried in Alacritty 0.7.2 and Tilix 1.9.4.
@mdom commented on GitHub (May 11, 2021):
This seems to be the same issue mentioned in gdamore/tcell#452 and #244. Although the work around mentioned #244 does not work on my system.
@mdom commented on GitHub (May 17, 2021):
This is fixed in gdamore/tcell@8f925d8 and works fine on my machine. Maybe it would be good to update the dependency on tcell to release 2.3.1?
@D54 commented on GitHub (May 25, 2021):
I can confirm that the current version works perfectly with gdamore/tcell v2.3.3.
c723ed0solved this issue as well, so it can be closed.