EasyManua.ls Logo

Cisco Touch10 User Manual

Cisco Touch10
43 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #20 background imageLoading...
Page #20 background image
20
D1535805 User Guide In-Room Control for Touch10. Produced June 2017 for CE9.0. © 2015–2017 Cisco Systems, Inc. All rights reserved
Group Button
Widgets
Groups of either two, three or
four buttons with custom text are
available. The buttons within a group
are linked so that only one can be
selected at a time (also known as
radio buttons).
In the Properties panel you will be
oered to specify the width of the
Group buttons — see also “A Tour of
the In-Room Control Editor” on page
9 for more on width adjustments.
The size of the button determines
the maximum number of characters
you can add. Text does not wrap
to a new line. You cannot use the
SetValue
command to change the
text dynamically.
Example of use: Room presets that
are mutually excluding, like room
presets where you can choose
between Dark, Cool, and Bright.
Remember to deselect (release)
the preset, if it is no longer valid (for
instance when changing the lights
with a wall control, or a Touch 10
slider.
About Group Buttons
Events
Example: There are four buttons in the group with WidgetId = “groupbutton”.
Press the button with GroupID = “two”.
Terminal mode
*e UserInterface Extensions Event Pressed Signal: “groupbutton:two
** end
*e UserInterface Extensions Event Released Signal: “groupbutton:two
** end
XML mode
<Event>
<UserInterface item=”1”>
<Extensions item=1>
<Widget item=”1”>
< A c t io n ite m = 1”>
<WidgetId item=”1”>groupbutton</WidgetId>
<Value item=”1”>two</Value>
<Type item=”1>released</Type>
</Action>
</Widget>
</Extensions>
</UserInterface>
</Event>
Pressed Triggered when one of
the buttons is pressed.
Value: The GroupID
of the button (within
the group) that was
pressed.
Released Triggered when one
of the buttons is
released.
Value: The GroupID
of the button (within
the group) that was
released
Commands
The visual appearance of the button changes
immediately when you tap it. However, the control
system must always send a SetValue command
to the video system when one of the buttons are
tapped. This ensures that the status is updated
accordingly.
Use the
UnSetValue
command to release all buttons
in the group so that no button is highlighted.
Example: Select (highlight) the button with GroupID = “one” in the group
with WidgetId = “groupbutton”. Then, release all buttons (no buttons are
highlighted).
xCommand UserInterface Extensions Widget SetValue
WidgetId: “groupbutton” Value: “one
xCommand UserInterface Extensions Widget UnsetValue
WidgetId: “groupbutton”

Other manuals for Cisco Touch10

Question and Answer IconNeed help?

Do you have a question about the Cisco Touch10 and is the answer not in the manual?

Cisco Touch10 Specifications

General IconGeneral
Display Size10.1 inches
Resolution1280 x 800 pixels
Touch TechnologyCapacitive
ConnectivityEthernet, Wi-Fi
PowerPower over Ethernet (PoE)
MountingTabletop or wall mount
ProcessorARM-based processor
CompatibilityCisco video conferencing systems

Summary

Introduction

Definition of Terms

Defines key terms used in the document related to video systems and control.

In-Room Controls

Explains how to customize the Touch 10/DX user interface for peripheral control.

What Is In-Room Control?

More About How In-Room Control Works

Creating a User Interface

Creating a User Interface for the Touch10

Guides on creating custom user interface panels for peripheral controls on the Touch10/DX.

Launch the In-Room Control Editor

Steps to access and start the In-Room Control Editor via the web interface.

A Tour of the In-Room Control Editor

Provides an overview of the In-Room Control Editor interface and its functionalities.

Application Programming Interface (API)

API for Programming In-Room Controls

Details how to connect to the video system and communicate using the API.

API for Programming In-Room Controls (Cont.)

Covers events for widget actions, distinguishing between terminal and XML output modes.

API for Programming In-Room Controls (Cont.)

Explains events for panel updates and page opening/closing.

API for Programming In-Room Controls (Cont.)

Discusses commands and statuses for widgets, including SetValue.

Widgets

Overview of Widgets

Introduces widgets as user interface elements and explains widget identifiers.

Switch

Describes the two-state switch widget, its events, and commands.

Slider

Details the slider widget for value selection, its events, and commands.

Button

Covers the button widget, its states, events, and commands.

Group Button

Explains the group button widget for linked selections, events, and commands.

Icon Button

Describes icon buttons, their behavior, events, and commands, similar to text buttons.

Spinner

Details the spinner widget for stepping through values, its events, and commands.

Text

Explains the text widget for displaying information, its events, and commands.

Directional Pad

Describes the directional pad widget, its buttons, events, and use cases.

Spacer

Explains the spacer widget as a layout tool with no associated events or commands.

Command Reference

Events

Details the various events sent by the video system for widget actions.

Events (Cont.)

Continues the description of events, including Widget Action and LayoutUpdated.

Commands

Lists and explains commands like SetValue, UnsetValue, and Clear.

Statuses

Explains how to retrieve widget status using the xStatus command.

Use of a Video Switch

Using a 3rd Party Video Switch to Extend the Number of Video Sources Available

Explains how to configure and use external video switches with the Cisco codec.

Command Details

Provides details on commands for managing external video sources.

Video Switch Example

Illustrates a practical setup and configuration for using a video switch.

Troubleshooting

Using the Development Tools on the Web Interface for Troubleshooting

Guides on using web interface tools like Log and Widget State Overview for troubleshooting.

Tips and Tricks

Recommended Best Practice

Offers best practices for event feedback, widget initialization, and panel updates.

Recommended Best Practice (cont.)

Continues best practices with examples for lights, temperature, blinds, and buttons.

Who Has Access?

Granting Access to In-Room Control Editor and Extensions API

Explains administrator rights and user account creation for accessing the editor.

Room Simulator

Running the Simulator

Provides instructions on how to launch and use the In-Room Control simulator.

Related product manuals