# Types

This section provides documentation for various types used in indicators. These types define the structure and behavior of indicator options and chart objects.

***

## Available Types

* [`AnchorPoint`](/fto-indicators-docs/types/anchor-point.md): Defines the text anchor point used for positioning text objects relative to their coordinates.
* [`TOptionType`](/fto-indicators-docs/types/option-type.md): Defines the type of an option parameter.
* [`TObjectType`](/fto-indicators-docs/types/object-type.md): Defines the types of chart objects that can be created.
* [`TOutputWindow`](/fto-indicators-docs/types/output-window.md): Defines where an indicator should be displayed on the chart.
* [`TPenStyle`](/fto-indicators-docs/types/pen-style.md): Defines the style of lines used in indicators and chart objects.
* [`TDrawStyle`](/fto-indicators-docs/types/draw-style.md): Defines how indicator values should be visually represented on the chart.
* [`ObjProp`](/fto-indicators-docs/types/object-property.md): Defines the properties that can be accessed for chart objects.
* [`TIndexBuffer`](/fto-indicators-docs/types/index-buffer.md): Represents a buffer for storing indicator values.
* [`TVisibleBufferInfo`](/fto-indicators-docs/types/visible-buffer-info.md): Represents the visual properties and information about an indicator buffer.
* [`FTODate`](https://gitlab.com/fto-docs/strategies/-/blob/indicators/Indicators/Types/fto-date.md): Represents a date and time value in the format of the trading platform.
* [`TimeValue`](/fto-indicators-docs/types/time-value.md): Represents a time value in the format of the trading platform.

***

Click on the type name to view its detailed documentation.


---

# Agent Instructions: 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://fto-2.gitbook.io/fto-indicators-docs/types.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.