> For the complete documentation index, see [llms.txt](https://docs.nedyx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nedyx.com/version-1.52-preview/clearlines-functions/general-aspects/calculated-widget-properties.md).

# Calculated widget properties

Some widget properties can be defined by formula. Here, the most important property is the content of a widget, which can be either entered manually during the Edit mode, or can be calculated by a formula.&#x20;

<figure><img src="/files/VJnJ8WNw035dRufX8w1B" alt=""><figcaption><p>The content of the cell widget is calculated by the RAND function.</p></figcaption></figure>

Besides the content, there are several other properties which can be calculated during a session, like Visible, Style or Connection. This provides the Editor with enhanced capabilities to dynamically customize the user interface and functionality of an app.&#x20;

If a property of a widget is calculated, the following principles are followed:

* A new calculation of a property replaces the previous value(s) of the property completely.
* If the calculation formula of a property returns *empty*, the property value(s) are not changed.
* When a value of a widget on which the property directly or indirectly depends changes, the formula of the property is recalculated.
* Calculated properties have different dimensionality. There are properties like *Content* or Editable, which can be a multi-cell range, or a property *Visible* or *Style*, containing always only one cell.

In the following chapters, these properties are described in detail.&#x20;


---

# 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.nedyx.com/version-1.52-preview/clearlines-functions/general-aspects/calculated-widget-properties.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.
