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

Update docs accordingly.

Browse Source
This commit is contained in:
Rodrigo Girão Serrão
2023-02-08 10:53:51 +00:00
parent bd719e057f
commit e5e7c08afe
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/blog/posts/on-dog-food-the-original-metaverse-and-not-being-bored.md
View File

@@ -288,7 +288,7 @@ So, thanks to this bit of code in my `Activity` widget...
parent.move_child( parent.move_child(
self, before=parent.children.index( self ) - 1 self, before=parent.children.index( self ) - 1
) )
self.emit_no_wait( self.Moved( self ) ) self.post_messa_no_wait( self.Moved( self ) )
self.scroll_visible( top=True ) self.scroll_visible( top=True )
``` ```

4
docs/examples/events/custom01.py
View File

@@ -25,8 +25,8 @@ class ColorButton(Static):
self.styles.border = ("tall", self.color) self.styles.border = ("tall", self.color)
async def on_click(self) -> None: async def on_click(self) -> None:
# The emit method sends an event to a widget's parent # The post_message method sends an event to be handled in the DOM
await self.emit(self.Selected(self, self.color)) await self.post_message(self.Selected(self, self.color))
def render(self) -> str: def render(self) -> str:
return str(self.color) return str(self.color)

2
docs/guide/events.md
View File

@@ -110,7 +110,7 @@ The message class is defined within the widget class itself. This is not strictl
## Sending events ## Sending events
In the previous example we used [emit()][textual.message_pump.MessagePump.emit] to send an event to its parent. We could also have used [emit_no_wait()][textual.message_pump.MessagePump.emit_no_wait] for non async code. Sending messages in this way allows you to write custom widgets without needing to know in what context they will be used. In the previous example we used [post_message()][textual.message_pump.MessagePump.post_message] to send an event to its parent. We could also have used [post_message_no_wait()][textual.message_pump.MessagePump.post_message_no_wait] for non async code. Sending messages in this way allows you to write custom widgets without needing to know in what context they will be used.
There are other ways of sending (posting) messages, which you may need to use less frequently. There are other ways of sending (posting) messages, which you may need to use less frequently.