Releases · darrenburns/textual-autocomplete

28 Mar 10:00

v2.1.0b0

d569256

This release adds support for newer versions of Textual.

Note that on Textual 0.16.0, there may be small visual glitches when tabbing between Inputs which use autocompletes. This bug is fixed inside Textual itself and the fix will be part of Textual 0.17.0, which should drop this week.

What's Changed

Textual v0.14.0 compat by @UmBsublime in #12
feat: only react to key events (and stop them) when dropdown is displayed by @jtyers in #9
feat: only show dropdown if input widget currently has focus by @jtyers in #8

New Contributors

@UmBsublime made their first contribution in #12
@jtyers made their first contribution in #9

Full Changelog: v2.0.0b0...v2.1.0b0

Contributors

UmBsublime and jtyers

Assets 2

17 Feb 21:32

darrenburns

v2.0.0b0

e14aeae

v2.0.0b0 - Custom completion callbacks, small API changes

Support custom completion logic: when you select an item from a dropdown, you are now able to pass a callback function giving fine-grained control over the new state of the input.
Encapsulated cursor_position and value into a new InputState object.

Assets 2

17 Feb 18:44

darrenburns

v1.2.0b0

eab9957

v1.2.0b0 - Option to retain focus on Input after using Tab key to complete

Previously, when you press the Tab key to select a completion, the Input would be filled with the chosen value and focus would go to the next widget in Textual's focus chain.

Now, this behaviour is disabled by default. Pressing the Tab key to select an item in the dropdown will still fill the item, but it won't move focus. The input will behave as normal after the completion - so you can press Tab again to switch focus.

The previous functionality is still available via a new tab_moves_focus boolean switch available on the AutoComplete class.

Assets 2