You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by and-viceversa December 1, 2024
How can I temporarily disable the command palette and its binding?
My application makes use of the command palette but there are times when it'd be nice to temporarily disable it as well.
For example, there might be a temporary Screen with a "Yes/No/Cancel" type option flow. If the command palette is accessible, the user can pivot away from that screen without choosing an available option.
Reading through the App source, the command palette is pretty tightly coupled to the App itself. ENABLE_COMMAND_PALETTE is typed as a ClassVar so I can't modify that from within my App instance.
Another possible method is to disable the command palette at the application level, and then reimplement the Binding for each Screen. That seems like either I've missed something simple or too hacky an approach.
The text was updated successfully, but these errors were encountered:
Discussed in #5316
Originally posted by and-viceversa December 1, 2024
How can I temporarily disable the command palette and its binding?
My application makes use of the command palette but there are times when it'd be nice to temporarily disable it as well.
For example, there might be a temporary Screen with a "Yes/No/Cancel" type option flow. If the command palette is accessible, the user can pivot away from that screen without choosing an available option.
Reading through the App source, the command palette is pretty tightly coupled to the App itself.
ENABLE_COMMAND_PALETTE
is typed as aClassVar
so I can't modify that from within my App instance.Another possible method is to disable the command palette at the application level, and then reimplement the
Binding
for each Screen. That seems like either I've missed something simple or too hacky an approach.The text was updated successfully, but these errors were encountered: