> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/reference/howto/wrong-scaling-of-pascom-client.md).
# Workaround for wrong scaling of the PASCOM App
With this workaround you can fix a wrong scaling of the PASCOM App on Windows.
In special cases, it can happen that the scaling of the PASCOM App does not look correct. This only affects Windows users and only in certain monitor/resolution combinations. This workaround should help to improve the scaling of the PASCOM App.
### PASCOM App scaling not correct, what can be done?
If the control elements of the PASCOM App appear either too small or too large, adjusting the HiDPI scaling of Windows can be helpful. Instead of scaling the application itself, this can be done via Windows.
Close your PASCOM App and then right-click on the shortcut to the PASCOM App and select the menu item **"Properties"**. There, switch to the **"Compatibility"** tab. Depending on the Windows version, the settings for high DPI (HiDPI) are now available here.
By adjusting the HiDPI scaling, you can achieve an optimal size of the PASCOM App controls to ensure a pleasant and legible user experience. Please note that changing the HiDPI scaling can lead to a blurred font display.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pascom.net/en/reference/howto/wrong-scaling-of-pascom-client.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 `build a script that syncs our docs to a CMS` 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.
