From 99d482491b68645824692542c20abfe1f4c4c9d0 Mon Sep 17 00:00:00 2001 From: Dave Pearson Date: Wed, 1 Mar 2023 09:14:27 +0000 Subject: [PATCH] A warning from the future Add a warning to my first blog post, letting the attentive reader know that `emit_no_wait` doesn't exist any more, and linking them to what they should be using if they want to do their own custom messages. --- ...n-dog-food-the-original-metaverse-and-not-being-bored.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/blog/posts/on-dog-food-the-original-metaverse-and-not-being-bored.md b/docs/blog/posts/on-dog-food-the-original-metaverse-and-not-being-bored.md index 076cb96b5..5e91cd825 100644 --- a/docs/blog/posts/on-dog-food-the-original-metaverse-and-not-being-bored.md +++ b/docs/blog/posts/on-dog-food-the-original-metaverse-and-not-being-bored.md @@ -300,6 +300,12 @@ So, thanks to this bit of code in my `Activity` widget... self.save_activity_list() ``` +!!! warning + + The code above used `emit_no_wait`. Since this blog post was first + published that method has been removed from Textual. You should use + [`post_message_no_wait` or `post_message`](/guide/events/#sending-messages) instead now. + ### Pain points On top of the issues of getting to know terminal-based-CSS that I mentioned