Cisco TelePresence SX10 Manual - Página 24

Navegue en línea o descargue pdf Manual para Sistema de conferencias Cisco TelePresence SX10. Cisco TelePresence SX10 45 páginas. In-room control on touch 10
También para Cisco TelePresence SX10: Manual de instalación (8 páginas), Manual del usuario (26 páginas), Manual rápido (2 páginas), Manual del usuario (34 páginas), Manual del usuario (29 páginas), Manual de usuario preliminar (9 páginas), Manual del usuario (38 páginas), Manual de instalación (8 páginas), Manual del usuario (2 páginas), Manual del usuario (37 páginas), Manual (45 páginas), Manual de instalación (2 páginas), Manual del usuario (34 páginas), Manual del usuario (5 páginas), Manual del usuario (38 páginas), Manual del usuario (38 páginas), Manual de introducción (46 páginas), Manual rápido (2 páginas)

Imprimir página
Cisco TelePresence SX10 Manual

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
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
© 2016 Cisco Systems, Inc.
All rights reserved.
interface. A value of
"inactive"
Text
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>
<UserInterface item="1">
<Extensions item="1">
<Widget item="1">
<Action item="1">
<WidgetId item="1">button</WidgetId>
<Value item="1"></Value>
<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"
24
command to change the
SetValue
Group
buttons.
XML mode