Skip to content
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

Investigate responsiveness of BINDINGS #8

Open
bluematt opened this issue Apr 19, 2023 · 4 comments
Open

Investigate responsiveness of BINDINGS #8

bluematt opened this issue Apr 19, 2023 · 4 comments

Comments

@bluematt
Copy link
Owner

No description provided.

@bluematt
Copy link
Owner Author

I'm not sure how BINDINGS work. I thought they were contextual based on the Widget with the current focus (or its nearest parent with BINDINGS) but that doesn't appear to be the case.

@davep
Copy link

davep commented Apr 20, 2023

Bindings on a widget will only be available when focus is within a widget, that's correct. Although you do also need to keep in mind that any bindings on the app or on a screen will also be in play too.

Do yell with an example if you're finding that's not the case.

@bluematt
Copy link
Owner Author

I haven't seen the docs that say they are cumulative, although I had kind of worked that out. ¯_(ツ)_/¯

I'll need to rethink them, so the UI isn't swamped with options.

@davep
Copy link

davep commented Apr 21, 2023

If it helps: an approach I'm starting to take with any non-trivial application like this is to show=False almost all bindings, and then only show the most important ones. One such important one being F1 to show all the help and keys.

Screenshot 2023-04-21 at 09 12 39
At some point I'm minded to try and create a HelpScreen screen that will dumpster-dive the bindings and auto-generate something.

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

No branches or pull requests

2 participants