alihan/textual
1
0
Fork 0
mirror of https://github.com/Textualize/textual.git synced 2025-10-17 02:38:12 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1346 from davep/bug/1342/inherited-movement-keys

Browse Source 
Add support for a `PRIORITY_BINDINGS` classvar to work alongside `BINDINGS`
This commit is contained in:
Will McGugan
2022-12-16 20:13:31 +00:00
committed by GitHub
parent 62d5810c04 4ee1aba436
commit d11e3f2e15
9 changed files with 704 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/guide/input.md
View File

@@ -127,6 +127,15 @@ Note how the footer displays bindings and makes them clickable.
Multiple keys can be bound to a single action by comma-separating them.
For example, `("r,t", "add_bar('red')", "Add Red")` means both ++r++ and ++t++ are bound to `add_bar('red')`.
!!! note
Ordinarily a binding on a focused widget has precedence over the same key binding at a higher level. However, bindings at the `App` or `Screen` level always have priority.
The priority of a single binding can be controlled with the `priority` parameter of a `Binding` instance. Set it to `True` to give it priority, or `False` to not.
The default priority of all bindings on a class can be controlled with the `PRIORITY_BINDINGS` class variable. Set it to `True` or `False` to set the default priroty for all `BINDINGS`.
### Binding class
The tuple of three strings may be enough for simple bindings, but you can also replace the tuple with a [Binding][textual.binding.Binding] instance which exposes a few more options.