> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-buffer-display.md).

# Messages View Buffer Display

The [Messages view](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view.md) buffer display (Figure 1) is a window into the world of network messages and signals received and transmitted by Vehicle Spy. Toolbars both [above](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-top-toolbar.md) and [below](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-bottom-toolbar.md) the display contain many features to adjust its appearance to fit desired needs.

![Figure 1: The Messages view buffer display.](/files/YjbJlZh1HfQJE9jf45HY)

On the far left side is a [buffer progress display](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-buffer-display/buffer-progress-display.md) bar that shows how full the buffer is. Next to that are **+/- buttons** that can be clicked to [show or hide signals](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-buffer-display/displaying-signals-in-messages-view.md) defined within each message.

The following icons indicate data defined in the [Messages Editor](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/messages-editor-overview.md):

![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/MysteryMsgIcon.gif) Unknown message that is not defined.\
![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/RxMsgIcon.gif) Receive message.\
![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/TxMsgIcon.gif) Transmit message.\
![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/DBaseMsgIcon.gif) [Database](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-setup/network-databases.md) message.\
![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/DefinedSignalIcon.gif) Defined signal.

Clicking on an icon opens a convenient [task menu](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-buffer-display/messages-view-task-menus.md) for performing common tasks quickly.

Clicking in the main display area highlights the entire row in green for easy reading. Activity highlighting helps pinpoint changing data. Gray indicates fast changing data (rate <= 1s). Blue indicates slow changing data (rate > 1s). Data that stops changing gradually has its highlighting fade to white.

A horizontal scrollbar lets you see any [columns](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-column-headers.md) hidden from view. A vertical scrollbar lets you see messages hidden from view in static mode or review message history while [paused](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-top-toolbar/pause-messages-view.md) in scrolling mode.

Please check the following video for more details.

{% embed url="<https://youtu.be/_YMMon-QX84?feature=shared>" %}


---

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

```
GET https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view/messages-view-buffer-display.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.