Crestron
e-control Vote SW-VOTE
44
••
Server Configuration In Depth
Installation & Reference Guide — DOC. 5822
Each RTS queue should be defined as either a Standard Scrollers or a Custom
Scrollers, similar to the one pictured below:
A Standard Scroller Signal Block Definition window,
showing the defintiion of the QUEUE1 scroller from demo1.
Set the (enabled) options as follows.
•
Default query number
This value needs to point to a query (
i.e.,
have the same value as the
ID
field of a record
in the
Queries
table) which describes access to an RTS table. See the “Database”
section below for the specifics on how to create these queue query records and their
associated RTS tables.
N
OTE
:
For your convenience, five (5) such records and tables are supplied in the sample
database file. There are also nine (9) “save files” (tables, actually) for each. The ID numbers
of these supplied records are 1 through 5. (Note that demo2 uses the first two.)
•
List rows (r) [In Use]
Enter here the number of rows to be displayed on the touchpanel. Value must not exceed
the value of
List rows (r) [Defined]
.
•
List columns (c) [n Use]
RTS queue scrollers require a minimum of 2 columns. The first column is used for the
seat’s screenname; the second for the seat’s state mark. You are free to define additional
columns if you like. For example, you might want to display seat number, district, and/or
party affiliation along with the other information.
•
Sort
This option should be
by ID field
for scrollers to be used as RTS queues. This makes the
names in each queue display in chronological order (in the order they entered the queue).
N
OTE
:
It is not critical to set this yourself. For RTS queue scrollers, this option is forced to
by ID field
when applying the settings (
i.e.,
when leaving the
Configuration Settings
window).
For more information on defining scrollers, see the SW-DBM manual, Doc. 5823.