Cisco TelePresence MX700 Manuel - Page 16

Parcourez en ligne ou téléchargez le pdf Manuel pour {nom_de_la_catégorie} Cisco TelePresence MX700. Cisco TelePresence MX700 45 pages. Single camera on a free standing floor stand or a floor stand secured to the wall
Également pour Cisco TelePresence MX700 : Manuel d'installation (32 pages), Manuel de démarrage rapide (12 pages), Manuel d'installation (28 pages), Manuel d'installation (29 pages), Manuel d'installation (32 pages), Manuel de référence rapide (2 pages), Manuel (45 pages), Manuel d'installation (29 pages), Manuel de référence rapide (2 pages), Manuel de référence rapide (2 pages), Manuel de démarrage (46 pages)

Imprimer la page

Events for widget actions

Table of contents

The video system sends one or more of the following events when someone

uses the controls on the Touch 10 in-room control panel:

Introduction

•

Pressed

•

Changed

Create a user interface

•

Released

API for in-room control

•

Clicked

Widgets

Command reference

UserInterface Extensions Event

Troubleshooting

One single string contains information about the type of action, which widget

triggered the event (identified by the Widget ID), and the widget value.

Tips and tricks

How to register:

xfeedback register event/UserInterface/Extensions/Event

Examples

Example:

*e UserInterface Extensions Event Pressed Signal: "

** end

*e UserInterface Extensions Event Changed Signal: "

** end

*e UserInterface Extensions Event Released Signal: "

** end

*e UserInterface Extensions Event Clicked Signal: "

** end

D15358.01 APRIL 2016

Collaboration Endpoint software

version 8.1

- sent when a widget is first pressed

- sent when changing a widget's value

(applies only to toggle buttons and sliders)

- sent when a widget is released

(also when moving out of the widget before releasing)

- sent when a widget is clicked

(pressed and released without moving out of the widget)

(suited for terminal output mode)

Type of action

Two event versions that a control system can register to: one suited for terminal output mode, the other for XML output mode

These events are sent in two versions.

• UserInterface Extensions Event

• UserInterface Extensions Widget - suited for XML output mode

Refer to the table below to find out which version is best suited for your control

system to register to.

When, and by which widgets (user interface elements), these events are

triggered, are described in the

UserInterface Extensions Widget

The type of action, which widget triggered the event (identified by the

Widget ID), and the widget value are included as separate elements in the

XML tree.

How to register:

xfeedback register event/UserInterface/Extensions/Widget

Example:

WidgetId

Value

<Event>

WidgetId

Value

WidgetId

Value

WidgetId

Value

</Action>

</Widget>

</Extensions>

</UserInterface>

</Event>

- suited for terminal output mode

Widgets

chapter.

(suited for XML output mode)

WidgetId

</WidgetId>

Value

</Value>

Type

</Type>

Type of action