> 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/getting-started/interacting-with-nodes-in-the-designer-viewer/navigating-your-logicnets.md).

# Navigating Your Logicnets

### Navigation by Mouse

Simple logicnets can be viewed on screen with no navigation, but as your logicnets get larger and longer, navigating the Viewer screen is easy using the mouse to drag and drop the logicnet to show the area of interest in the middle of the screen. You can also zoom in and out using a mouse scroll wheel or other standard mouse/pad feature.

If you need to, there are also specific feature buttons, grouped together in the Navigator on the bottom-left of the Viewer screen.

### Navigator Tools

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7f02cc8c6b21ce74d95d343eaae828b959d82aed%2F651be0c0-deb5-46be-be81-c03ab13b4182.jpg?alt=media) To expand or collapse the navigator tools, click the arrow next to the word "navigator".

The navigator contains **zoom** buttons that allow you to zoom in and out on your logicnet. These increase or decrease the size of your logicnet in the Viewer.

**Redraw** resubmits the page to the system, which refreshes the graph in the Viewer. This is most frequently used when you work in manual layout mode (Visual Navigation Framework only).

**Center** allows you to re-center your logicnet in the Viewer screen, which can be helpful if you are working on nodes at the bottom of a large logicnet and need to quickly reorient yourself.

If you are working in manual layout mode (Visual Navigation Framework only), you will see the **manual** button is enabled. You can also enable manual layout mode by clicking this button. With manual mode enabled, the grid button is enabled, which tells the system to display a grid on the Viewer to help you with layout precision.

In the move to field you can type in a node number or a portion of the node label and the system will take you to that node, highlight the node, and center it on the page. This allows you to go directly to a specific node if you know its node number or label. Partial search is possible. - the first match is found and highlighted.

### Expert Tips

Sometimes your logicnet may "disappear" from the screen when you inadvertently move the mouse with the viewer graph active. When this happens, just click on **center** to bring the logicnet back into view.

Another useful technique to prevent your logicnets getting too unwieldy is to break them up into smaller parts, and "call" each part sequentially. Use a string of [call nodes](/release-9/platform-documentation/process-nodes/call-node.md), one for for each subnet.


---

# 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/getting-started/interacting-with-nodes-in-the-designer-viewer/navigating-your-logicnets.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.