> For the complete documentation index, see [llms.txt](https://wfsys.gitbook.io/workflow-forms-syntax/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wfsys.gitbook.io/workflow-forms-syntax/workflow_forms/conditions/event_condition/double_click_condition.md).

# DoubleClickCondition

## Шаблон DoubleClickCondition <a href="#template_double_click_condition" id="template_double_click_condition"></a>

```xml
<Condition Name="" Type="DoubleClickCondition" Assembly="Conditions">
  <!--Тэги, общие для всех условий-->
  <AlwaysChange Value="" />
  <!--Тэги, специфичные для DoubleClickCondition-->
  <Object Name="" />
  <Button Type="" />
</Condition>
```

## Описание DoubleClickCondition <a href="#description_double_click_condition" id="description_double_click_condition"></a>

```xml
<Condition Name="DoubleClickConditionName" Type="DoubleClickCondition" Assembly="Conditions">
  <!--Тэги, общие для всех условий-->
  <!--Тэги, специфичные для DoubleClickCondition-->
</Condition>
```

## Тэги, специфичные для DoubleClickCondition <a href="#tags_double_click_condition" id="tags_double_click_condition"></a>

### Object <a href="#object" id="object"></a>

[Объект](/workflow-forms-syntax/workflow_forms/objects.md), на котором срабатывает событие двойного клика.

Необязательный тэг. Значение тэга `<Object>`: не ожидается.

Если тэг `<Object>` отсутствует, то событие срабатывает для формы.

```xml
<Object Name="ObjectName" />
```

#### Атрибуты тэга `<Object>` <a href="#attributes_tag_object" id="attributes_tag_object"></a>

<table data-header-hidden><thead><tr><th align="center"></th><th width="502.3333333333333"></th></tr></thead><tbody><tr><td align="center">Name</td><td><p>Название объекта.</p><p></p><p>Обязательный атрибут. Ожидается название одного из объектов, описанных в форме.</p></td></tr></tbody></table>

### Button <a href="#button" id="button"></a>

Кнопка мыши, нажатая во время клика.

Необязательный тэг. Значение тэга `<Button>`: не ожидается.

Если тэг `<Button>` отсутствует, то для атрибута `Type` используется значение Any.

```xml
<Button Type="Any" />
```

#### Атрибуты тэга `<Button>` <a href="#attributes_tag_button" id="attributes_tag_button"></a>

<table data-header-hidden><thead><tr><th align="center"></th><th width="502.3333333333333"></th></tr></thead><tbody><tr><td align="center">Type</td><td><p>Тип нажатой кнопки.</p><p></p><p>Обязательный атрибут. Ожидается название одного из <a href="#mouse_button_types">типов кнопок мышки</a>.</p></td></tr></tbody></table>

#### Типы кнопок мышки <a href="#mouse_button_types" id="mouse_button_types"></a>

<table data-header-hidden><thead><tr><th align="center"></th><th width="502.3333333333333"></th></tr></thead><tbody><tr><td align="center">Any</td><td>Любая кнопка</td></tr><tr><td align="center">Left</td><td>Левая кнопка</td></tr><tr><td align="center">Right</td><td>Правая кнопка</td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://wfsys.gitbook.io/workflow-forms-syntax/workflow_forms/conditions/event_condition/double_click_condition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.