> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/visual-navigation-framework/visual-navigation-framework-resize-a-node.md).

# Visual Navigation Framework: Resize a Node

In manual layout a node can be resized to accommodate a label or indicate

## Resize the Node Using the Mouse

1\. Click on a node. A red outline is added on the node to indicate that this node is selected. 2. Hover over the right or bottom side of a node: the mouse pointer is changed to resize 3. Click on the side of the node and keep the mouse button pressed and move the mouse. The size of the node is updated accordanly and will snap to the grid lines. When the ALT-key is pressed during dragging small-step resizing is possible.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f916058dc4c1f7ccea8a9a75759c0dfbfe2d1915%2F0cbf7075-9be0-4537-8e61-2693a6bb74c2.gif?alt=media)

## Edit a Node Label

To edit a node label:

* right click on the node
* choose edit label
* type label name

To split a long node label into multiple lines follow above steps then

* click on HTML
* insert\
  wherever a line break has to be added.
* Save your changes

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-b6150767baf947934fa3b102ff52da899ae3226a%2F8ef03558-34a5-4fef-9b1c-79ec2ea4a2ec.jpg?alt=media)

## Edit a Layout Parameter

1\. Open the node context menu (right-click on node) 2. Choose 'Edit layout info'-option 3. A popup is opened which shows the node position (and the node size) 4. The node position and node size can be edited 5. Click the save button to apply the new layout-parameters.

**Note**: When using the edit-layout-parameters popup, all edges connected to this node are re-connected ready for re-formatting.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3bec3d2f770c8e60cc88c538c4b1cc84402056bf%2F8fb62990-6bf0-458b-8f19-65fb6d638a37.gif?alt=media)


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/visual-navigation-framework/visual-navigation-framework-resize-a-node.md?ask=<question>&goal=<user_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.
