> For the complete documentation index, see [llms.txt](https://docs.iceteagroup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iceteagroup.com/general/ported-application/project-structure/visual-styles.md).

# Visual Styles

Window's Visual Style mode can be enabled/disabled for all PPJ controls by setting the *SalApplication.VisualStyles* flag to true in the *Main* method when the application starts up.

When Visual Styles styles are on, there are some differences of behavior that need to be taken into account:

* ListBox control generates the LBN\_SELCHANGE notification when the mouse is clicked on the empty area. Therefore, with XP styles on, ListBox controls in ported applications receive a SAM\_Click event when clicked on the empty area.
* The TabControl used in SalQuickTabs, which is the native .NET TabControl that wraps Windows Common Controls, does not support the owner draw mode when XP styles are turned on, therefore disabled tabs cannot be painted as disabled. Additionally, if the orientation of the tabs is different from Top, the tabs are drawn in standard mode because XP does not support painting the tabs in any other orientation.
* Buttons that should not get the focus, typically on a toolbar, do get the focus anyway when XP styles are turned on.

{% hint style="info" %}
The *SalApplication.VisualStyles* flag can be overridden by using the startup switches /xp or /noxp or /visualstyles=on|off.
{% endhint %}


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.iceteagroup.com/general/ported-application/project-structure/visual-styles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.