Rane HAL1x Design Guide - Page 124

Best Practices, What are some best practices to follow when creating and working with HAL System con

Get Rane HAL1x PDF manuals and user guides View all Rane HAL1x manuals
Add to My Manuals
Save this manual to your list of manuals

Page 124 highlights

HAL SYSTEM DESIGN GUIDE There are a few situations, however, in which your choices for Link Master are limited or are made for you: l If one of the participants is a read-only control, the read-only control is always the Link Master because its value cannot be changed by software. In this situation, the ability to change the Link Master is disabled. l Dynamic selectors (such as the Selector on DR2s and DR3s) cannot be Link Master because they have no value when they are not active in a control link. The ability to configure dynamic selectors as the Link Master is disabled. In summary, there are three ways in which a control link's Link Master designation is created: 1. You create the control link. 2. You manually change the Link Master designation for the control link. 3. You add a read-only control to the control link. NOTE: Because Command control links do not maintain a state or hold a value, these control links do not need a Link Master. Best Practices What are some best practices to follow when creating and working with HAL System control links? BEST PRACTICE: Always drop any new control link participant onto a control already participating in the link. In other words, the control link target1 should always be an existing participant. Think in terms of what it is that you want to control. BEST PRACTICE: Name your links as you create them to help with identification later. For example, if you want to see the links in which a control is participating, the list of links will only make sense if each one is aptly named. 1The control onto which you will drop one or more other controls to create a control link. Think of the control link target as a bucket into which you place all the other controls participating in the link. 120

  • 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
There are a few situations, however, in which your choices for Link Master are limited or are made
for you:
l
If one of the participants is a read-only control, the read-only control is always the Link
Master because its value cannot be changed by software. In this situation, the ability to
change the Link Master is disabled.
l
Dynamic selectors (such as the Selector on DR2s and DR3s) cannot be Link Master because
they have no value when they are not active in a control link. The ability to configure
dynamic selectors as the Link Master is disabled.
In summary, there are three ways in which a control link's Link Master designation is created:
1.
You create the control link.
2.
You manually change the Link Master designation for the control link.
3.
You add a read-only control to the control link.
NOTE
:
Because Command control links do not maintain a state or hold a value, these control links do
not need a Link Master.
Best Practices
What are some best practices to follow when creating and working with HAL System con-
trol links?
BEST PRACTICE
:
Always drop any new control link participant onto a control already participating in
the link. In other words, the
control link target
1
should always be an existing participant. Think in
terms of what it is that you want to control.
BEST PRACTICE
:
Name your links as you create them to help with identification later. For example, if
you want to see the links in which a control is participating, the list of links will only make sense if
each one is aptly named.
1
The control onto which you will drop one or more other controls to create a control link. Think of the control
link target as a bucket into which you place all the other controls participating in the link.
HAL SYSTEM DESIGN GUIDE
120