Cisco TelePresence SX10 Manuel - Page 24

Parcourez en ligne ou téléchargez le pdf Manuel pour {nom_de_la_catégorie} Cisco TelePresence SX10. Cisco TelePresence SX10 45 pages. In-room control on touch 10
Également pour Cisco TelePresence SX10 : Manuel d'installation (8 pages), Manuel de l'utilisateur (26 pages), Manuel rapide (2 pages), Manuel de l'utilisateur (34 pages), Manuel de l'utilisateur (29 pages), Manuel d'utilisation préliminaire (9 pages), Manuel de l'utilisateur (38 pages), Manuel d'installation (8 pages), Manuel de l'utilisateur (2 pages), Manuel de l'utilisateur (37 pages), Manuel (45 pages), Manuel d'installation (2 pages), Manuel de l'utilisateur (34 pages), Manuel de l'utilisateur (5 pages), Manuel de l'utilisateur (38 pages), Manuel de l'utilisateur (38 pages), Manuel de démarrage (46 pages), Manuel rapide (2 pages)

Imprimer la page

Button with custom text

Table of contents

Introduction

Example of use: Room presets for lighting, for example three buttons

Create a user interface

that show Dark, Cool, Bright.

API for in-room control

Events

Pressed

Widgets

Released

Command reference

Clicked

Troubleshooting

Tips and tricks

Examples

In-Room Control on Touch 10

for Cisco TelePresence

MX200 G2, MX300 G2,

MX700, MX800,

SX10, SX20, SX80

Collaboration Endpoint

software version CE8.2

Commands

D15358.02 - JULY 2016

www.cisco.com

Use the

interface. A value of

"inactive"

Text

inactive

active

Triggered when the button is pressed

Value: N/A

Triggered when the button is released

Value: N/A

Triggered when the button is released

Value: N/A

command to highlight or not the button in the user

SetValue

will highlight the button, and a value of

"active"

will release it.

Buttons with custom text come in different sizes. The size determines

the maximum number of characters you can add. Text does not wrap

to a new line. You cannot use the

text dynamically.

A button has two states: active and inactive. You do not have to set

the button in active state when someone taps it; the button can be

used to just send a signal without changing the button's visual state.

If you want to have the buttons linked so that only one can be

selected at a time (radio buttons), consider to use

Example:

Press and release the button with WidgetId = "button".

Terminal mode

*e UserInterface Extensions Event Pressed Signal: "button"

** end

*e UserInterface Extensions Event Released Signal: "button"

** end

*e UserInterface Extensions Event Clicked Signal: "button"

** end

<Event>

<WidgetId item="1">button</WidgetId>

<Type item="1">clicked</Type>

</Action>

</Widget>

</Extensions>

</UserInterface>

</Event>

Example:

Highlight the button with WidgetId = "button" (set it in

active state).

xCommand UserInterface Extensions Widget SetValue WidgetId: "button"

Value: "active"

command to change the

SetValue

Group

buttons.

XML mode