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

Remove some trailing whitespace

Browse Source
This commit is contained in:
Dave Pearson
2022-10-13 11:03:17 +01:00
parent 78ea2cd9f8
commit f127506e60
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/guide/screens.md
View File

@@ -10,7 +10,7 @@ Textual requires that there be at least one screen object and will create one im
!!! tip !!! tip
Try printing `widget.parent` to see what object your widget is connected to. Try printing `widget.parent` to see what object your widget is connected to.
<div class="excalidraw"> <div class="excalidraw">
--8<-- "docs/images/dom1.excalidraw.svg" --8<-- "docs/images/dom1.excalidraw.svg"
@@ -30,7 +30,7 @@ Let's look at a simple example of writing a screen class to simulate Window's [b
=== "screen01.css" === "screen01.css"
```sass title="screen01.css" ```sass title="screen01.css"
--8<-- "docs/examples/guide/screens/screen01.css" --8<-- "docs/examples/guide/screens/screen01.css"
``` ```
@@ -59,7 +59,7 @@ You can also _install_ new named screens dynamically with the [install_screen][t
=== "screen02.css" === "screen02.css"
```sass title="screen02.css" ```sass title="screen02.css"
--8<-- "docs/examples/guide/screens/screen02.css" --8<-- "docs/examples/guide/screens/screen02.css"
``` ```
@@ -96,7 +96,7 @@ You can also push screens with the `"app.push_screen"` action, which requires th
### Pop screen ### Pop screen
The [pop_screen][textual.app.App.pop_screen] method removes the top-most screen from the stack, and makes the new top screen active. The [pop_screen][textual.app.App.pop_screen] method removes the top-most screen from the stack, and makes the new top screen active.
!!! note !!! note
@@ -115,7 +115,7 @@ You can also pop screens with the `"app.pop_screen"` action.
### Switch screen ### Switch screen
The [switch_screen][textual.app.App.switch_screen] method replaces the top of the stack with a new screen. The [switch_screen][textual.app.App.switch_screen] method replaces the top of the stack with a new screen.
<div class="excalidraw"> <div class="excalidraw">
--8<-- "docs/images/screens/switch_screen.excalidraw.svg" --8<-- "docs/images/screens/switch_screen.excalidraw.svg"
@@ -139,7 +139,7 @@ Screens can be used to implement modal dialogs. The following example pushes a s
=== "modal01.css" === "modal01.css"
```sass title="modal01.css" ```sass title="modal01.css"
--8<-- "docs/examples/guide/screens/modal01.css" --8<-- "docs/examples/guide/screens/modal01.css"
``` ```
@@ -147,5 +147,5 @@ Screens can be used to implement modal dialogs. The following example pushes a s
```{.textual path="docs/examples/guide/screens/modal01.py" press="q,_"} ```{.textual path="docs/examples/guide/screens/modal01.py" press="q,_"}
``` ```
Note the `request_quit` action in the app which pushes a new instance of `QuitScreen`. This makes the quit screen active. if you click cancel, the quit screen calls `pop_screen` to return the default screen. This also removes and deletes the `QuitScreen` object. Note the `request_quit` action in the app which pushes a new instance of `QuitScreen`. This makes the quit screen active. if you click cancel, the quit screen calls `pop_screen` to return the default screen. This also removes and deletes the `QuitScreen` object.