Rane HAL1x Design Guide - Page 156

What is the difference between a toggle and selector event? And why, where and when would I use, each?

Page 156 highlights

HAL SYSTEM DESIGN GUIDE monitor the current state. To allow end users to change the event status, provide an additional control to activate (Lunch) or deactivate (Band) the selector event. Any 2-position selector in Halogen can be linked to a selector event, including: l 2-position selector preset l 2-position selector or router block in the Processing Workspace l 2-position selector on a DR2, DR3, DR6, Web Control page or 3rd-pary control screen l 2-position selector in a Paging Station or Pager1 (to select one of two Scenarios using time of day) What is the difference between a toggle and selector event? And why, where and when would I use each? Toggle events are always presented and displayed using a checkbox. If your event can be easily understood by end users using a single term with a checkbox next to it, use a toggle. Or put another way, if the end user label easily suggests an on and off state, or an active and inactive, use a toggle. Examples are: l Open l Applause l On Air l Happy Hour l Worship In Session l System Power On l SPL exceeded l Emergency l Intermission l Recording l Caution, Bridge Up l Sorry, We're Closed l Chairman Override On l Quiet Please l Page Active in Zone 6 l Room 105 A&B Combined l Noise Masking On l Stage Door Locked l Overflow On l Balcony Open l Time Out, Dude However, a selector event always displays two terms along with two radio buttons - each with a text label. One radio button and its text label is selected when the event is active or on. And the second button/label is selected when the event is inactive or off. Thus, a selector event is used to indicate or show an end user that there are two possible conditions where on and off do not make sense. Examples include: l Lunch / Band l Worship mode / Rehearsal mode 152

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

monitor the current state. To allow end users to change the event status, provide an additional control to acti-
vate (Lunch) or deactivate (Band) the selector event.
Any 2-position selector in Halogen can be linked to a selector event, including:
l
2-position selector preset
l
2-position selector or router block in the Processing Workspace
l
2-position selector on a DR2, DR3, DR6, Web Control page or 3rd-pary control screen
l
2-position selector in a Paging Station or Pager1 (to select one of two Scenarios using time of day)
What is the difference between a toggle and selector event? And why, where and when would I use
each?
Toggle events
are always presented and displayed using a checkbox. If your event can be easily understood
by end users using a single term with a checkbox next to it, use a toggle. Or put another way, if the end user
label easily suggests an on and off state, or an active and inactive, use a toggle. Examples are:
l
Open
l
Applause
l
On Air
l
Happy Hour
l
Worship In Session
l
System Power On
l
SPL exceeded
l
Emergency
l
Intermission
l
Recording
l
Caution, Bridge Up
l
Sorry, We’re Closed
l
Chairman Override On
l
Quiet Please
l
Page Active in Zone 6
l
Room 105 A&B Combined
l
Noise Masking On
l
Stage Door Locked
l
Overflow On
l
Balcony Open
l
Time Out, Dude
However, a
selector event
always displays two terms along with two radio buttons – each with a text label.
One radio button and its text label is selected when the event is active or on. And the second button/label is
selected when the event is inactive or off. Thus, a selector event is used to indicate or show an end user that
there are two possible conditions where on and off do not make sense. Examples include:
l
Lunch / Band
l
Worship mode / Rehearsal mode
HAL SYSTEM DESIGN GUIDE
152