From c14c0fccc38685e83273360b610a124053472335 Mon Sep 17 00:00:00 2001 From: Will McGugan Date: Sat, 18 Sep 2021 16:46:56 +0100 Subject: [PATCH] elaborate on naming convention of handlers --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f580c96ba1..b7b75d741c 100644 --- a/README.md +++ b/README.md @@ -71,7 +71,7 @@ Beeper.run() Here we can see a textual app with a single `on_key` method which will handle key events. Pressing any key will result in playing the terminal bell (generally an irritating beep). Hit Ctrl+C to exit. -Event handlers in Textual are defined by convention, not by inheritance (so you won't find an `on_key` method in the base class). Each event has a `name` attribute which for the key event is simply `"key"`. Textual will call the method named `on_` if it exists. +Event handlers in Textual are defined by convention, not by inheritance (there's no base class with all the handlers defined). Each event has a `name` attribute which for the key event is simply `"key"`. Textual will call the method named `on_` if it exists. Let's look at a _slightly_ more interesting example: