What's so special about Esc?

[pebezo]

I have flow where I have 3 TableView(s) that are turned on/off as one goes from A, to B, to C. I'd like to use Esc as the "go back" button in this flow. By default Esc is mapped to close the app, so I changed this to F10 using:

Application.QuitKey = Key.F10;

To make Esc work, in the main window I'm overriding the KeyDown to react to the "back" key, like this:

        KeyDown += (sender, key) =>
        {
            if (key == Key.Esc || key == Key.F2)
            {
                key.Handled = true;
                GoBack();
                Draw(); // doesn't seem to matter
            }
        };

The GoBack() is the function that turns the appropriate TableViews on/off (in addition to other stuff).

What I'm seeing is that if I use the F2 key everything works perfectly. However, if I use the Esc key, it works only sometimes... The actual view changes, but it's like the screen is not being updated?

For example 1) I hit Esc 2) seemingly nothing happens on screen 3) I hit the down arrow key and now the screen is refreshed and it's now showing the appropriate TableView. If I were to hit Esc twice in a row, on the second Esc I can quickly see the two screens getting refreshed one after another. It's like the first Esc was paused and when I hit Esc again it "runs" both of them one after another.

Thoughts?

[tznind]

What driver are you using?

Does it reproduce if you use NetDriver (Application.UseSystemConsole before init)?

Typically you don't call Draw but instead call SetNeedsDisplay

Only thing special about Escape is tied up in console escape codes (AKA Terminal Sequences) but this should be unlikely to affect things.

What version of nuget package are you using?

[BDisp]

I understand what you mean. I don't know if it was CanFocus but the changed code above seems to not reproduce the related issue.

[tznind]

I don't see a difference between your code @BDisp and @pebezo except for the _current -1.

But I also don't see the Esc being ignored behaviour. It just seems to work for me.

[BDisp]

And newCurrent >= -1.

[tznind]

@pebezo does the new code fix problem for you?

Also by 'artifacts with NetDriver' do you mean the corners? This seems to be an odd situation where the curved corner rune renders correct on WindowsDriver but not NetDriver. The workaround is to use regular corners (although I agree they are less pretty :)

So options are

• Try @BDisp code to see if it fix
• Switch to NetDriver and use square corners
• Wait for v2 drivers and see if it improves situation

_container = new Window
{
    X = 0,
    Y = 0,
    Width = Dim.Fill(),
    Height = Dim.Fill(),
-  BorderStyle = LineStyle.Rounded,
    SuperViewRendersLineCanvas = true,
    CanFocus = true,
    TabStop = TabBehavior.TabStop
};

[pebezo]

Try @BDisp code to see if it fix

This improves the UX (starts at the first table), but it starting at the second spot was actually intentional because (for some reason) it's easier to reproduce the problem this way. Starting with the first table still happens, but you have to work at it a bit more.

This only happens if we press the Enter and "Esc" quickly.

I'm able to reproduce it by waiting around 1s between clicks (maybe a bit less).

Switch to NetDriver and use square corners

Yes, the square corners is what I was talking about. I'd rather take this Esc issue with an alternate key as workaround instead.

Wait for v2 drivers and see if it improves situation

Yes, I think this is probably the best option. Most of the users would probably use it on a non-Win device, where this is not an issue.

Thank you all for looking into this 👍