# setVisibility

### Parameters

1. controlId - id of the brixxbox control as a string
2. visible - (optional, default = true) bool value if the control should be visible or not
3. subControl (optional) Some controls have sub Controls, that can be set visible or hidden. **Important: setVisibility for subcontrols cannot be used in onAppStart, because some controls are not fully created at that time, use onAppInitialized instead**. Here is a list of possible subControls:
   * grids - The grid toolbar has to be active to see buttons at all!
     * buttons - shows or hides the buttons of a grid
     * buttonNew - shows or hides the new buttons of a grid
     * buttonDelete - shows or hides the delete buttons of a grid
     * buttonCopy - shows or hides the copy buttons of a grid

### Example Usages

1\. To show a control

```javascript
   brixxApi.setVisibility("myControlId");
   brixxApi.setVisibility("myControlId", "visible"); 
   brixxApi.setVisibility("myControlId", true);
```

2\. To hide a control

```javascript
   brixxApi.setVisibility("myFieldId", false);
```

3\. Hide the grid new button

```javascript
   brixxApi.setVisibility("myGrid", false, "buttonNew");
```


---

# Agent Instructions: 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:

```
GET https://brixxbox.gitbook.io/brixxbox-documentation/client-api-reference/functions/setvisibility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.