Skip to content

fix(keys): initially focus the key log #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

TomJGooding
Copy link

When running textual keys, currently the 'Clear' button will have initial focus. This can be confusing if you're trying to test the enter key with some modifiers, as this might invoke a button press!

This simply re-orders the composed widgets so the key log is initially focussed instead.

When running `textual keys`, currently the 'Clear' button will have
initial focus. This can be confusing if you're trying to test the
`enter` key with some modifiers, as this might invoke a button press!

This simply re-orders the composed widgets so the key log is initially
focussed instead.
@willmcgugan
Copy link
Contributor

I would have gone with AUTO_FOCUS="KeyLog" myself!

@TomJGooding
Copy link
Author

Sure, that also works, but why? This does the same thing and reflects the order of the widgets as they are displayed.

@willmcgugan
Copy link
Contributor

I think the addition of the classvar makes it more explicit which is focused, but honestly I'm not fussed either way...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants