Textual 0.24.0 adds a Select control¶
Coming just 5 days after the last release, we have version 0.24.0 which we are crowning the King of Textual releases. At least until it is deposed by version 0.25.0.
The highlight of this release is the new Select widget: a very familiar control from the web and desktop worlds. Here's a screenshot and code:
from textual import on from textual.app import App, ComposeResult from textual.widgets import Header, Select LINES = """I must not fear. Fear is the mind-killer. Fear is the little-death that brings total obliteration. I will face my fear. I will permit it to pass over me and through me.""".splitlines() class SelectApp(App): CSS_PATH = "select.tcss" def compose(self) -> ComposeResult: yield Header() yield Select((line, line) for line in LINES) @on(Select.Changed) def select_changed(self, event: Select.Changed) -> None: self.title = str(event.value) if __name__ == "__main__": app = SelectApp() app.run()
This one required new functionality in Textual itself. The "pull-down" overlay with options presented a difficulty with the previous API. The overlay needed to appear over any content below it. This is possible (using layers), but there was no simple way of positioning it directly under the parent widget.
We solved this with a new "overlay" concept, which can considered a special layer for user interactions like this Select, but also pop-up menus, tooltips, etc. Widgets styled to use the overlay appear in their natural place in the "document", but on top of everything else.
A second problem we tackled was ensuring that an overlay widget was never clipped.
This was also solved with a new rule called "constrain".
constrain to a widget will keep the widget within the bounds of the screen.
In the case of
Select, if you expand the options while at the bottom of the screen, then the overlay will be moved up so that you can see all the options.
These new rules are currently undocumented as they are still subject to change, but you can see them in the Select source if you are interested.
In a future release these will be finalized and you can confidently use them in your own projects.
Fixes for the @on decorator¶
@on decorator is proving popular.
To recap, it is a more declarative and finely grained way of dispatching messages.
Here's a snippet from the calculator example which uses
The decorator arranges for the method to be called when any of the four math operation buttons are pressed.
In 0.24.0 we've fixed some missing attributes which prevented the decorator from working with some messages.
We've also extended the decorator to use keywords arguments, so it will match attributes other than
There is a surprising number of fixes in this release for just 5 days. See CHANGELOG.md for details.
If you want to talk about this update or anything else Textual related, join us on our Discord server.