> 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-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-drop-down-list.md).

# Graphical Panel Controls: Drop Down List

A Drop Down List control allows input from a list of items. The elements of the list can be either manually entered within the control or taken from the list of name/value pairs in a state-encoded signal.

![Figure 1: A Drop Down List control with four options, the third of which is currently selected.](https://3170208387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL6lcovCpkhoS9uTOFtEp%2Fuploads%2F7aGWcrF9fjW2pNyAwzY3%2FgpctrlDropDownList.gif?alt=media\&token=88350dd6-c527-4188-8a2d-84503eef76ff)

In addition to the [Common Control Properties](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-common-control-properties.md) that apply to all controls, the Drop Down List control has an additional property described in Table 1.

**Table 1: Drop Down List Control Properties**

| Property | Function and Options                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| List     | Double-click this entry to bring up a dialog box where you can enter the items for the list and the values they represent (Figure 2). Simply type a name in the **List Item** box and a matching value in the **Value** box, then click the **Add** button or press Enter. Vehicle Spy will add the item to the list in the bottom of the dialog, and automatically increment the **Value** counter for the next item as a convenience. You can also click **Load From Signal** to import name/value pairs from a state-encoded signal. |

![Figure 2: Entering data elements into a Drop Down List control.](https://3170208387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL6lcovCpkhoS9uTOFtEp%2Fuploads%2Fc3dYi6V5bvYom8sLN4VQ%2FgpctrlDropDownList_Setup.gif?alt=media\&token=3378b957-dc61-46f8-b0c4-6e69d956808e)


---

# 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://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-drop-down-list.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.