> 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-move-a-node.md).

# Visual Navigation Framework: Move a Node

Because applications that use the Visual Navigation framework display the actual logicnet graph to users, the placement of nodes is important. When you are modeling your logicnets you can move the nodes of the logicnet using both the mouse and the keyboard.

## Mouse

1. Select a node by clicking on it.
2. Drag the node using your mouse and the system will snap the load to the grid line. When you perform this action while pressing the ALT key on your keyboard, the system positions the node exactly at the current mouse cursor position.
3. Release the mouse button to complete the action.

## Keyboard

1. Select a node.
2. Press an arrow key to move the node in any direction.
3. Press the shift + arrow key to move the node in small steps.

## Edit Layout Parameters

1. Open the node context menu by right-clicking on the 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**: Using the edit-layout-parameters popup. All edges connected to this node are rerouted.


---

# 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-move-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.