mirror of
https://github.com/Textualize/textual.git
synced 2025-10-17 02:38:12 +03:00
Add a FAQ about some keys not making it to Textual apps
This commit is contained in:
17
FAQ.md
17
FAQ.md
@@ -7,6 +7,7 @@
|
||||
- [How can I select and copy text in a Textual app?](#how-can-i-select-and-copy-text-in-a-textual-app)
|
||||
- [How do I center a widget in a screen?](#how-do-i-center-a-widget-in-a-screen)
|
||||
- [How do I pass arguments to an app?](#how-do-i-pass-arguments-to-an-app)
|
||||
- [Why do some key combinations never make it to my app?](#why-do-some-key-combinations-never-make-it-to-my-app)
|
||||
- [Why doesn't Textual look good on macOS?](#why-doesn't-textual-look-good-on-macos)
|
||||
- [Why doesn't Textual support ANSI themes?](#why-doesn't-textual-support-ansi-themes)
|
||||
|
||||
@@ -173,6 +174,22 @@ Greetings(to_greet="davep").run()
|
||||
Greetings("Well hello", "there").run()
|
||||
```
|
||||
|
||||
<a name="why-do-some-key-combinations-never-make-it-to-my-app"></a>
|
||||
## Why do some key combinations never make it to my app?
|
||||
|
||||
Textual can only ever support key combinations that are passed on by your
|
||||
terminal application. Which keys get passed on can differ from terminal to
|
||||
terminal, and from operating system to operating system.
|
||||
|
||||
When [creating bindings for your
|
||||
application](https://textual.textualize.io/guide/input/#bindings) we
|
||||
recommend picking keys and key combinations that are supported on as many
|
||||
platforms as possible.
|
||||
|
||||
The easiest way to test different environments to see which
|
||||
[keys](https://textual.textualize.io/guide/input/#keyboard-input) can be
|
||||
detected is to use `textual keys`.
|
||||
|
||||
<a name="why-doesn't-textual-look-good-on-macos"></a>
|
||||
## Why doesn't Textual look good on macOS?
|
||||
|
||||
|
||||
22
questions/why-do-some-keys-not-make-it-to-my-app.question.md
Normal file
22
questions/why-do-some-keys-not-make-it-to-my-app.question.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: "Why do some key combinations never make it to my app?"
|
||||
alt_titles:
|
||||
- "Cmd key isn't working"
|
||||
- "Command key isn't working"
|
||||
- "Alt key isn't working"
|
||||
- "Ctrl and function key isn't working"
|
||||
- "Control and function key isn't working"
|
||||
---
|
||||
|
||||
Textual can only ever support key combinations that are passed on by your
|
||||
terminal application. Which keys get passed on can differ from terminal to
|
||||
terminal, and from operating system to operating system.
|
||||
|
||||
When [creating bindings for your
|
||||
application](https://textual.textualize.io/guide/input/#bindings) we
|
||||
recommend picking keys and key combinations that are supported on as many
|
||||
platforms as possible.
|
||||
|
||||
The easiest way to test different environments to see which
|
||||
[keys](https://textual.textualize.io/guide/input/#keyboard-input) can be
|
||||
detected is to use `textual keys`.
|
||||
Reference in New Issue
Block a user