> For the complete documentation index, see [llms.txt](https://manual.edgetx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.edgetx.org/edgetx-how-to/disable-touchscreen.md).
# Disable Touchscreen
There are various reasons on why you may want to disable the touchscreen. Unintentional touches during a flight could change your model configuration which can be a risk.
Therefore we can create a [global function](/color-radios/radio-settings/global-functions.md) or[ special function](/color-radios/model-settings/special-functions.md) using the **No Touch** feature to disable and enable the touch feature. While global functions apply to all models, the special function is defined on individual models.
## Disable touch screen with a global function
In the following example we use switch SF to disable the touch screen with a global function.
create a global function to disable touch with switch SF
show the global function
## Disable touch screen with a special function
Customizable switches or logical switches cannot be used in global functions. But we can use a special function to enable and disable the touch screen with a customizable switch.
setup of customizable switches
create a special function to disable touch with SW1
list of special functions
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://manual.edgetx.org/edgetx-how-to/disable-touchscreen.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
