User Manual - Sportstec Support

User Manual - Sportstec Support
SPORTSTEC
CODA
User Manual
Contents
Welcome to CODA© . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
CODA Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Current CODA Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CODA Support & Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Using this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
The Main Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1. The CODA Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
The Design Mode Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
a. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
b. Popup Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
c. Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
d. Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
e. Text Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
f. Slice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
g. Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
h. Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
i. Command Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
j. Inspector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Properties Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
j (i) Name an Event, Popup Tag or Tag Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
j (ii) Event Time Tweaks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
j (iii) Exclusive Link Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
j (iv) Hot Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
j (v) Tag Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
j (vi) Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Appearance Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
j (vii) Button Shapes and Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
j (viii) The Fill Panel–Button & Form Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
j (ix) The Stroke Panel – Button Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
j (x) Popup Tag Mat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
j (xi) Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
k. Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
l. Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
m. Link Action Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
n. The Code Mode Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
o. Saving and Retrieving your Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
p. Password Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2. Button Resizing & Reshaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
The Slice Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Building a CODA Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4. Creating and Specifying an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Reconfiguring an Event to a Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5. Creating and Specifying a Popup Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6. Creating and Specifying a Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Reconfiguring Tag and Event buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7. Importing an Image to the CODA Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.Duplicating CODA Form Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Advanced Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9. Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
a. Link Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Establish a link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Remove a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
b. Pass Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
c. Exclusive Link Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
d. Putting the Links Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
e. Event Button Reactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10. CODA Form Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
a. Arranging the Form in Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
b.Transparent Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
c. The Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
11. Email a Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
12. Coding an Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
13. CODA Command Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Activate iCODA for a Mobile Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Working in the Command Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
14. The CODA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Establishing a CODA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
15. Network Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
a. Connecting to a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
b. Creating a New Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
c. Connect to (Join) or Reconnect to a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
d. The Coding Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
e. The Session Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
f. Start Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
g. Session Timer and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
h. Disconnect from / Stop a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
i. Data Transfer and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
16. Exporting your Coded Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Interpreting CODA Event Log Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
(i) Keyboard Quick Key Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
(ii) Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
iCODA Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Current iCODA Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Linking iCODA to a Command Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Activation in a WiFi Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Remote Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Navigation between iCODA screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Gestures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Single tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Slide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Double tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Resize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Event Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Popup Tag Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Tag Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Shape Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Text Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Slice Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
List Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Open a Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Create a new Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Password Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Remove a Form or a Timeline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Edit a Form Name or Timeline Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Design Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Insert a new Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Move an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Resize an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Modify the properties of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Arrange Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Remove an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
5
Link Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Create a link between Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Delete a link between Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Inspector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Object Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Caption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Fill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Bevel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Stroke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Text & Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Inbound Action Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Tag Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Tag Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Form Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Code Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Start a Coding Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Coding History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Saving your Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Stop the coding session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Online Coding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
The Coding Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Create a New Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Connect to (Join) or Reconnect to a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Start a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Start Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Session Timer and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Disconnect from / Stop a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Data Transfer and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Email a Coding Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Email a Timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6
7
Welcome to CODA©
Welcome to CODA©
Quick, Live Event Coding
CODA © by Sportstec is the latest addition to the Sportstec family of products. CODA © is
designed to work in conjunction with Sportstec Gamebreaker, SportsCode™ and Studiocode™
video analysis systems, giving you activity and/or participant event coding capabilities
previously only dreamed of. The beauty of CODA © is the flexibility it gives coaching staff by
being able to code a performance either live at the venue, live from a remote location or at a
later time from pre-recorded footage.
CODA Overview
CODA is a tool that the User customizes to create a Log of Events, (the Event Log,) that can be
linked to a video. CODA is also a very flexible tool in that the Event Log can be exported into
Excel which makes the data available to be manipulated to produce a variety of reports to
compliment video replay analysis.
We recommend that you read sections 1 & 2 thoroughly to gain an understanding of the basis of
the CODA Structure – then work through Sections 3 – 10 which are written in a “Tutorial” format.
Here’s a quick guide to how the CODA process works.
CODA works in only 2 modes, Design Mode and Code Mode. In “Design Mode” you will design
the CODA Form that will determine what events you will code to the Event Log and what
descriptions you will make available to add to each of these events. In “Coding Mode” you will
use your designed CODA Form to build the event information on the Event Log.
In a new CODA Form you build, edit and categorize events or actions for future analysis. To do
this you create and name coded buttons for all actions. In sport for example you may wish to
code a particular player, a particular move, or each time a point(s) is scored.
Once you have built your CODA Form and customized it to provide you with the information
you need to enhance your existing instructional tools, when you click on or activate each Event
Button during coding it will mark the Event Log accordingly.
Gathering the data during the activity either live, (or later from video,) is easy. Now all that
is needed is for you to link the Event Log with a video timeline in one of the Sportstec
Gamebreaker, SportsCode™ or Studiocode™ video analysis systems. You can now analyze
performance according to the information on the timeline.
The captured Event Log data may also be exported into an Excel spreadsheet for separate
analysis.
Note: If CODA Event Log data is exported into a Sportstec Gamebreaker video analysis system,
only the Event Button data will be shown, there will be no tagged information about each event
written to a Sportstec Gamebreaker timeline.
8
System Requirements
System Requirements
The minimum recommended system requirements for CODA are :
Apple Computer with 1.5GHz or faster PowerPC G4 , PowerPC G5 , Intel Core Duo or Intel
Xeon processor
1 GB of RAM
50MB of HDD space
A display with 1024 x 768 resolution or higher
Mac OS X v10.4.11 or higher
(Optional) Tablet and pen
Current CODA Version
The current version of CODA which this Manual applies to is Version 2.0.0
Application Installation & Licensing
9
t
Insert the CODA CD into the CD-ROM drive on your computer or download the full
installer from the Sportstec website at www.sportstec.com
t
Run the installer package by double clicking on the installer found in the image. Once
the installer is complete, CODA can be found in the /Applications folder.
t
Launch CODA by double clicking on the CODA icon in the /Applications folder. The
following window will appear.
t
As a security measure, each time a software licence is either registered or deregistered
you will be required to enter the computer Administrators name and password before
being able to proceed with the
registration or deregistration
process. You are able to check your
Administrator name and your
system password by clicking on the
Apple symbol in the Main Menu bar,
then select System Preferences and
then Accounts.
CODA Support & Feedback
t
To register your CODA application online, click the “Register” button.
t
Enter your Registration Code and click the “Register” button.
If you have a Firewall that won’t allow you to register online, you may register manually. To effect
this process, click on the “Register Manually” button. CODA will provide you with a Licence code.
Email this code to [email protected] to receive an Activation Key. Enter both the Licence
code and the Activation Key into the relevant panels, then activate your software.
Software Updates
Sportstec Limited is constantly seeking enhancements to how this software can be used and
Sportstec welcomes User feedback for this purpose. You are able to download any
enhancements and update the software by clicking on “CODA ” at the far left of the Main Menu.
From the Sub-Menu selection click “About CODA ” to check which software version you are using,
and then from the same Sub-Menu select “Check For Updates”. If there are any software
upgrades available these may be downloaded.
CODA Support & Feedback
In order to keep Sportstec product software at the cutting edge, we invest heavily in research
and development. Sportstec is constantly providing it’s customers with innovations developed
from features and enhancements which have been driven by customer demand. Sportstec also
provides innovation that takes full advantage of advances in technology.
Sportstec has a rigorous testing process to ensure that all software is robust and fit for purpose.
Occasionally a bug will exist in spite of our best efforts to discover and eliminate it.
If you discover any fault or bug in CODA , please email [email protected] as soon as
possible. We aim to respond to you within 24 hours of your notification.
We would also welcome other feedback and comments regarding your ideas for a function or
feature which might be improved on or added.
If you require individual training in the CODA application, please contact your CODA distributor.
10
Using this Manual
Using this Manual
Sections 1 & 2 describe the functions which each of the Icons on the Toolbar performs.
Sections 3 – 8 describes how to create building blocks on your CODA Form.
Sections 9 – 11 describe how to assemble your building blocks into a working CODA model.
Section 12 describes coding your activity and editing the data.
Sections 13 - 15 describes how to link CODA desktop to iCODA (iPad, iPhone or iPod Touch).
Section 16 describes how to interpret the Data.
In this Manual references to Icons and Menu Headings are color coded to ease your
identification for Menu selection(s) as follows :
This Manual has been written with the assumption that the User is using an Apple Computer
with a standard mouse or trackpad and keyboard. References to “clicking” and cursor placement
are directly related to mouse or trackpad use.
Apple System Features which will speed up many of the CODA processes are inherent in the
CODA application. We recommend that you familiarize yourself with all the Apple system
features. We have explained some of these features in appendix (i) to this Manual but for a full
explanation you should consult your Apple Manual.
This manual contains links to a series of short video “tutorials”. You must be connected to the
Internet to activate the link. These links are marked by the following icon
Wherever this icon appears in the manual, click on the icon to view the video tutorial which will
demonstrate a feature or function of CODA which is described in the text alongside.
11
The Main Menu Bar
The Main Menu Bar
CODA has been written so that all the functions required of the application may be accessed
from the CODA Toolbar or by Control Click (right clicking) on menu links.
For the purpose of this manual, the functions of each of the Main Menu Headings in the Main
Menu Bar are summarized below.
CODA: With this Heading, the functions are limited to:
a). Registration & deregistration of your CODA licence.
b). CODA version updates.
c). In the “Preferences” sub-heading, you can choose to display a “Start up” window
on opening CODA.
d). The remaining functions are system functions.
FILE: The functions are all system functions with the exception of “Save Last Coding Session As...”,
(refer to para 1n for details on this function).
EDIT: The functions are all system functions with the exception of “Convert into Button”, and/or
“Convert into Event”, and/or “Convert into Tag”, (refer to paragraphs 4 & 6).
INSERT: The functions listed here may all be performed by clicking on the relevant icon in the
CODA Toolbar.
ARRANGE: The functions listed here are described in Paragraph 10a.
VIEW: The first 3 functions may also be performed by clicking on the relevant icon in the CODA
Toolbar. The remaining 7 functions may only be performed from this Menu and are described in
detail in Paragraphs 1.j (iv) ; 12 ; 1b and 3.
WINDOW: The functions are all system functions.
HELP: Contains this manual.
1. The CODA Toolbars
To open your CODA application select the CODA Icon
from your desktop or from the Dock.
This will open the “Document Startup Dialogue Window” . You may choose to bypass this
window by checking the box “Do not show this dialogue again”.
You may reinstate the Document Startup Dialogue by going to CODA in the Main Menu, select
Preferences and then check the box “Show Document Startup Dialogue”
12
1. The CODA Toolbars
When you place (hover) your cursor over each of the toolbar icons, a message will appear which
describes the function of the icon when you click on it.
You may open a new CODA Window by selecting “FILE” from the Main Menu then selecting “New
Form”. A CODA window becomes a CODA Form when you start placing coding objects in it.
You may open an existing Form by selecting “Open Form” or “Open Recent” and selecting your
target Form from where it is saved.
By default, when you select “Create New” the window will open in DESIGN MODE. When a Coding
Form is opened it will open in CODE MODE.
The Design Mode Toolbar
Click on “Design”to select the Design mode for CODA to operate in.
Clicking of an “EVENT” or “TAG” Icon will place a Code Button in the CODA Form. A button in the
Form must be “highlighted” before you can assign Properties or Appearance functions or Links
to it when you are designing your CODA Form. A “POPUP TAG” cannot be selected unless the
Event button to which it will be assigned is highlighted.
Click on a button to “highlight” it. It is highlighted when it is backlit with a
purple hue and becomes surrounded by eight (8) square re-sizing knobs;
one in each corner and one in the middle of each side. You may vary the
rounding in the button corners by dragging the purple dot in the top left
corner to the left (squares the shape) or to the right. A button can be moved around the CODA
Form by clicking on the centre of the button and dragging it to the desired location.
A button may be customized for easy recognition to differentiate it from other buttons in the
CODA Form and to set specific system parameters around how this marker will be used when
the Event Log is linked to and synchronized with a video timeline. Refer to paragraphs 2, 7 and
10 below for further details about button functionality.
A button may be named, functional properties attributed to it and the appearance of a button
may be manipulated by using the “INSPECTOR” function. (See paras. 1.j (i) – (xi) below).
Clicking of a “SHAPE” or “TEXT BOX” Icon will place a shape object in the CODA Form which may
contain colours, images or text. These shape objects have no coding function.
Clicking of a “CONTAINER” or “COUNTER” Icon will also place specialist objects on the Coding
Form. These objects and their functions are discussed in para graphs 1.j (vi) and 10c.
13
1. The CODA Toolbars
The Function and Purpose of each of the Toolbar Icons is as follows:
a. Events
When you place your cursor arrow over the Event icon the “Add an Event to
the Form” message appears. When, (and each time,) you click on this icon an
Event button will be placed in a descending vertical sequence on the left hand
side of the CODA Form. By default an Event button will be colored blue. This
will have a default caption “Event” in the centre of the button. This Event button
will be used to mark an event when the Event Log is synchronized to the
timeline in a SportsCode™ / Studiocode™ video analysis system.
An Event button may also be created by converting an existing Tag Button. This
can be achieved by Control Clicking on the target Tag button, and selecting
the “Convert into Event” option. You may also achieve this result by selecting
the “Convert into Event option from the Edit Menu in the Main Menu Bar. Be
aware that when you convert a Tag button into an Event button, the existing
aesthetic properties of the button, (name and appearance,) will be unchanged.
When an activity is being coded, clicking on an Event button will “activate” or
“deactivate” the button and at the same time mark the Log. The button may
deactivate itself automatically or may be required to be manually deactivated
depending upon whether or not the Lag Time function is active. (Refer to para.
1.j (ii) below). A button may also be automatically “activated” or “deactivated”
pursuant to Linking instructions. (Refer to Para. 1.j (iii) and 9 below.)
b. Popup Tag
When you place your cursor arrow over the Popup Tag icon the “Add a Popup
Tag to the Selected Event” message will appear. This icon will not be available
unless an Event button in the CODA Form is selected. A Popup Tag button has a
circle symbol in the top left corner of the button.
The purpose of a Popup Tag button is to enable you to code event descriptions
for the Event button and, (if you choose,) to describe consequent event results
and so on. They may also be tabulated for more focused analysis as part of the
analysis reporting that CODA can provide.
Refer to paragraph 5 below for further details about Popup Tag button
functionality.
When you click on this icon, (with an Event button selected,) a Popup Tag
button will be placed within a background panel referred to as a “Popup Tag
Mat” which will encompass / include / surround the selected Event button, (and
any prior created Popup Tag buttons which have been attributed to that Event
button) in the CODA Form. By default a Popup Tag will be colored yellow.
14
1. The CODA Toolbars
An alternative method is to select the Event button, Control Click and select
“Add Popup Tag”. A Popup Tag button can be moved to any location in the
CODA Form by clicking on the Popup Tag button and dragging it to the desired
location. The Popup Tag Mat which surrounds the Event button and the Popup
Tag button(s) will distort to remain linked to its Event button.
Popup Tag buttons are always only attached to one Event button.
The Popup Tag buttons on a Popup Tag Mat in the CODA Form can be hidden
and redisplayed by Control Clicking on the Event button and selecting “Hide/
Show Popup Tags” or by clicking on VIEW from the Main Menu and selecting
“Hide/Show Popup Tags”.
c. Tag
When you place your cursor arrow over the Tag icon the “Add a Tag to the
Form” message will appear. When, (and each time,) you click on this icon a Tag
button will be placed in a descending vertical sequence on the left hand side
of the CODA Form. A Tag button has a circle symbol in the top left corner of the
button. By default a Tag button will be colored yellow. A Tag can be moved to
any location in the CODA Form by clicking on the Tag and dragging it to the
desired location.
A Tag button may also be created by converting an existing Event Button. This
can be achieved by Control Clicking on the target Event button, and selecting
the “Convert into Tag” option. You may also achieve this result by selecting the
“Convert into Tag option from the Edit Menu in the Main Menu Bar. Be aware
that when you convert an Event button into a Tag button, the existing aesthetic
properties of the button, (name and appearance,) will be unchanged. Note: You
will not be able to perform this function if the Event button has Popup Tags
associated with it.
A Tag is initially identified as a yellow oblong button. A Tag is a descriptor
which will be attached to an Event marker (or instance when impoted into
SportsCode or Studiocode). A Tag is global in the sense that if it is not attached
to any specific Event by a link then it will mark all Events which are active at
the time the Tag is activated. If a Tag A is linked to another Tag B with the link
instruction to “activate and pass tag” then the “global” property for Tag A is
automatically disabled and it will activate and tag only Tag B. If a Tag is linked
to another Tag with the “Activate and pass tag” instruction, (or in a chain of Tags
which terminates in a link to an Event button) or to an Event, then the Tag will
pass its descriptor information or mark the Event in accordance with the link
instructions. Refer to paragraph 9 below for further details about this button
functionality with links.
A Tag may be set up to pass its descriptor to an Event which is not yet active
only if the Tag is set up as a source button in an On-activation Link and one
15
1. The CODA Toolbars
of the Link properties is to pass the Tag information forward. Refer to para. 9
below for more detailed information on this property.
d. Shape
When you place your cursor arrow over the Shape icon the “Create a new Shape”
message will appear. When, (and each time,) you click on this icon a Shape
button will be placed in a descending vertical sequence in the CODA Form.
The purpose of a Shape is to help organize your buttons visually, which can
make the coding process easier – especially live. You may color it , change
its shape etc to use as a background mat. A Shape button has no coding
function(s).
e. Text Box
When you place the cursor arrow over the Text Box icon the “Create a new Text
Box” message will appear. When, (and each time,) you click on this icon the
word “Text” within an oblong box that has 2 resizing knobs on both sides will
be placed in a descending vertical sequence in the CODA Form. This box has no
coding properties and its function is purely to place text at your selected place
in the CODA Form. The Text Box can be manually resized in the horizontal plane
and it will be automatically resized in the vertical plane to accomodate the
amount of text. The text can be selected to be aligned left, right or centered
within the text area.
f. Slice
The Slice tool will not be accessible unless an Event/Popup Tag/Tag button is
selected which has an image filling it. When you place the cursor arrow over
the Slice icon the “Slice an Event/Popup Tag/Tag” message will appear. When
you click on this icon the cursor will convert to a knife symbol which will then
allow you to slice the button.
The purpose of this tool is to provide a mechanism where a button, which has
an image filling it, can be separated into the component parts of the image and
each part will become a button which will possess the same properties as the
original.
g. Counter
When you place your cursor arrow over the Counter icon the “Create a new
counter” message will appear. When, you click on this icon the Counter will
place a transparent box in the Coding Form which contains the number 0.
16
1. The CODA Toolbars
The Counter has 3 functions to choose from when the Counter is linked to an
Event button. Refer to paragraph 1.j (vi)
h. Container
When you place the cursor arrow over the Container icon the “Create a new
Container” message will appear. When, (and each time,) you click on this icon a
Container Form will be placed in the CODA Form. Be mindful that if a Container
is selected, any objects created will be placed inside this container.
The purpose of the Container is to manage the available screen real estate for
your Coding Form. Refer to para. 10c for more detailed information.
i. Command Centre
When you place your cursor arrow over the Command Centre icon an “Open
Coda Command Centre” message will appear. When, you click on this icon the
Command Centre window will open.
The Command Centre allows you to connect to an iCODA application
installed on your iPad, iPhone or iPod Touch; activate or deactivate the iCODA
application and transfer CODA documents and output files. The Command
Centre is also used to establish a CODA Server.
NB : This feature is an Apple platform application only ie. It does NOT work for other
PDA devices
j. Inspector
When you place the cursor arrow over the Inspector icon the “Show or Hide
the Inspector Window” message will appear. Click on the Inspector icon with a
button in the CODA Form highlighted.
symbol, (which will be backlit with a sky blue hue,) to expose
Click on the
the “Properties Window”, which will allow you to specify the button properties.
symbol, (which will be backlit with a sky blue hue,) to expose
Click on the
the “Appearance Window” , which will allow you to determine how your button
and/or button combination(s) will appear.
symbol, (which will be backlit with a sky blue hue,) to
Click on the left
expose the “Outbound Action Links” display. What is displayed are the actions
consequent upon this button being activated or deactivated.
symbol, (which will be backlit with a sky blue hue,)
Click on the right
to expose the “Inbound Action Links” display. What is displayed are the actions
caused to this button because of the actions of other buttons linked to this
button.
17
1. The CODA Toolbars
Properties Windows
There is no Properties Window available for a Shape button or a Container.
18
1. The CODA Toolbars
j (i) Name an Event, Popup Tag or Tag Button
This function is the same for Event buttons, Popup Tag buttons and Tag buttons. With the button
highlighted, in the “Code Name” panel of the Inspector Properties function, type the caption that
will describe the Event and for Popup Tag and Tag buttons, the caption that will describe related
actions. In this case “Banana” has been chosen as the description of an Event button for a
hypothetical activity of selecting fruit from an assorted fruit basket. You may also name a button
by clicking on the button caption and then typing a new caption
The default setting places this description, (or Caption,) centrally within the target
button. You may move the Caption either within the borders of the button either
horizontally or vertically by highlighting the button, then select the Inspector
Appearance Window and clicking on and dragging the “Caption” sliders. If you
prefer you may also move the Caption outside the borders of the button.
Wherever you move a Caption to, it will remain relative to the button borders even though you
may subsequently choose to move or re-size the button.
To Show or Hide the Caption in the button, tick on the Check box to show it and
turn the display of the Caption off by clicking on the Caption box to deselect it.
You may change the color and typeface of the caption by selecting the button then opening the
Inspector, (refer to the Appearance section below). You may also change the caption font or color
by highlighting the button then clicking on the “FONTS” or the “COLORS” icon from the Toolbar.
A drop down window will appear which will present you with a variety of standard Font options
or the color palette options.
19
1. The CODA Toolbars
j (ii) Event Time Tweaks
This is a function for Event buttons only. You have complete control over the duration of each
event you code. Using the Lead and Lag Times means you can program CODA to automatically
add a specific time to the beginning or end of an event marked for the purpose of editing
a video when CODA is linked to a timeline in
the Sportstec Gamebreaker, SportsCode™ or
Studiocode™ application. In this illustration, 5
seconds Lead Time and 10 seconds Lag Time have
been selected.
1. The purpose of the Lead Time selection box is to set a predetermined period that the replay
video clip will start before the timepoint that the event is activated. In the illustration above, the
Timeline is marked and the linked video is set to commence 5 seconds before the time the Event
button was clicked.
2. The Lag Time selection box has 2 purposes:
(i) When the Lag Time box is not ticked, it will require the coding operator, (when the activity is
being coded,) to mark the timeline when the video clip will stop by clicking on the Event button
to manually deactivate it. When a Lag Time box is ticked and a time specified, then the Event
button will be deactivated automatically, the timeline marked (and the video clip will stop,) after
the period (in seconds,) specified.
(ii) Because the Lag Time will determine how long you have from when the Event button is first
activated until the Event button will be automatically deactivated, this has a coding significance.
When an Event button is activated any Popup Tag buttons associated with the Event will also
become available, but they will only remain available for as long as the Event button is active. ie.
The Lag Time specified will be the time limit available to code any Popup Tag description(s)
related to the event.
j (iii) Exclusive Link Cluster
This is a function exclusive to Event Buttons. The purpose of the “Exclusive Link Cluster” window
within the “INSPECTOR” function is to group Event buttons in the CODA Form which will be
mutually exclusive in their activation.
Para. 9 describes the function of Linking buttons in the CODA Form.
This will simplify the CODA Form by relieving you of having a large number of link lines
cluttering the CODA Form. It will also simplify the coding workload by deactivating any active
button in the cluster when another button in the cluster is activated.
20
1. The CODA Toolbars
j (iv) Hot Keys
This function is the same for Event buttons, Popup Tag buttons and Tag buttons. You may choose
to attribute a keyboard Hot Key or a combination of keys to any button. This will allow you to use
your mouse and/or your keyboard to activate a button while you are coding in a live
environment. To provide for this option, click on the Text box from the “Hot Key” panel at the
bottom of the Inspector window and then type in your keyboard option preference.
If a Hot Key has been nominated, it will be displayed in the top left corner of the button. You may
also display or hide all the Hot Key combinations in the button titles in the CODA Form by
clicking on the CODA Form and from the “VIEW” menu select “Show/Hide All Hot Keys”.
j (v) Tag Group
To ease your post-activity analysis, you may group nominated Tags together.
To establish a Tag Group, follow the same procedure as for the establishment of an “Exclusive
Link Cluster” as described in section 8.
j (vi) Counter
A Counter must be linked to an Event button to function. It can only be linked to one object.
If you attempt to link it to another object, it will deactivate the link which exists and activate
the new link. When a Counter is linked to an Event button, it will either count and display the
number of times that button has been activated to mark a complete instance, or count and
display the accumulative time period that the button has been active, or the last time period
that the button has been active on an activation by activation basis.
21
1. The CODA Toolbars
Appearance Windows
The Appearance Window for an Event button is
illustrated at left.
The Appearance Windows for a Popup Tag and Tag
are the same as for an Event button except there is
no Popup Tag Mat section.
The Appearance Window for a Shape button has all
the functions that an Event has except for the Text
Attributes, the ability to bevel the button and the
Popup Tag Mat.
The Appearance Window for a Text Box and a
Counter provides Text Attributes and Geometry
options only.
The Appearance Window for a Container provides
Shape, Fill, Stroke and Geometry options.
The Appearance Window for the Coding Form has
a background color fill provision only.
22
1. The CODA Toolbars
j (vii) Button Shapes and Images
This function is the same for Event buttons, Popup Tag buttons, Tag buttons and Shape buttons.
If you wish to graphically represent different button events you may change the shape of a
button or import an image to use as the button. A button may also be made transparent for use
with more advanced coding. The following 4 shape options are available within the drop down
menu. These shapes may be manipulated by using the re-sizing knobs.
By default, all button shapes except “Filled Image’s” will have a 1 point Stroke border.
A button in the CODA Form may be re-sized pursuant to the instructions detailed in para. 2
below.
j (viii) The Fill Panel–Button & Form
Presentation
Button Presentation
This function works the same for Event buttons, Popup Tag buttons, Tag buttons, Shape buttons,
Text Boxes and the Form background. The “Fill” panel allows you to color the button by clicking
on the color box in the Fill panel. The Colors palette will drop down. Click on the button color
you want from your preferred palette. The color will change to your selected color in the Button
in the Form, the color bar and in the Inspector Fill panel display. If you want to use a color from
the color favorites bar at the base of the color palette, drag and drop it either directly to the
Event button in the CODA Form; to the Color Bar at the top of the Colors drop down window; or
to the color box within the “Fill” panel in the Inspector window. The Gradient option (Event
button and Popup Tags only) in the Fill panel provides the ability to fill the button with a color
gradient vertically or horizontally.
You may also choose to make your button transparent by selecting no color as your choice. Refer
to para. 10b below – Transparent Buttons.
23
1. The CODA Toolbars
You may also choose to use an image as a button. With the button highlighted
open the “INSPECTOR” and from the “Shape” panel drop down menu select the
“Filled Images” option. Then from the “Fill” panel select “Image”. A File List window
will open. Navigate to and select the image you wish to use and double click on it.
The image will replace the target button.
If you wish to change an image, highlight the button and from the “Fill” panel select “Choose
Image”. Again the File List window will open.
The “Fill” panel in the Inspector window will change when you select this button to show the
image and to provide further options for Image button re-sizing.
You may now need to manipulate the image. First use the resizing knobs to get
the image to a size and shape that is suitable. If the image does not fit the required
shape, or if during the shape and size manipulation the image has become
distorted, you can restore image integrity by selecting one of the options in the
Image drop down menu which best suits your needs.
If you had previously placed a name in the Event button this name will remain in the button
overlaid on the image. To remove the name if the image portrays the event, with the Event
button selected, select the “INSPECTOR” icon and deselect the “Caption” box by removing the
tick from the box.
Form Presentation
In the same way as the “Inspector – Fill” function may be used to fill a button, it
may also be used to manipulate the background of the Form. By default the Form
background is white with a blue grid pattern. To change the background to a color
of your choice or to an image, with the “INSPECTOR” open, place the cursor within
the Form, but clear of any object, and click to open the Form Appearance window.
From the Fill options make your selection.
24
1. The CODA Toolbars
j (ix) The Stroke Panel – Button Presentation
This function is the same for Event buttons, Popup Tag buttons, Tag buttons and Shape buttons.
The “Stroke” panel scribes a border outline around the button. By default the Stroke is the same
color as the button background. If you click on the horizontal bar in the Stroke panel you will
have 4 border pattern options to choose from. If you click on the colored panel underneath the
“Stroke” box, a color chart will appear. Select the color you want the button outline to be, and
then click on the numbered size box on the right of the panel to set the width of the outline
which will be drawn from the existing outside of the box in.
j (x) Popup Tag Mat
This function is limited to an Event button. When a Popup Tag button is created, a Popup Tag Mat
will be drawn which surrounds the Event button and the Popup Tag button associated with it.
Any subsequent Popup Tag buttons which are created and associated with the Event button will
also be included in that same Tag Mat. The Popup Tag Mat has a very important function when
you are coding.
If your cursor goes off the Popup Tag Mat when you are coding the whole Popup Tag selection
will be deactivated and you must return your cursor to the Event button without clicking on the
button to reactivate it to continue entering Popup Tag information.
You can choose to vary the size of the border of a Popup Tag Mat by highlighting the Event
button and from the Inspector window selecting the size in the numbering box in the “Popup
Label Mat” panel. The higher the number, the larger the border will become.
You may also choose a color for the Popup Tag Mat by clicking on the color well on the left of the
“Popup Tag Mat” panel. A color palette window will open. Select the color you prefer and click on
your color choice.
25
1. The CODA Toolbars
j (xi) Geometry
This function is the same for Event buttons, Popup Tag buttons, Tag buttons, Shape buttons, Text
Boxes, Counters and Containers
This function allows you to vary the position of an object and the size of an object in the CODA
Form or within a Container Form very precisely.
If you highlight the target object, the objects position in the Form will be precisely described
with reference to the top left hand corner of the object from the top left corner of the Form.
These reference values are shown in the “Origin” boxes. The “X” and “Y” are references to the axis
of the Form.
The size of the object may be varied by changing the values in the “Size” boxes. These values will
vary the “Width” and the “Height”, with reference to the top left of the object. If an object has a
shape, then the reference is to the top left of the 8 resizing knobs.
The position of the button may be locked by checking the “Locked” box. This will prevent the
button from being moved within the Form no matter what other positioning or repositioning of
buttons or combinations of buttons may occur. To turn this function off, re-check the box.
k. Colors
When you place the cursor arrow over the Colors icon the “Show Color Panel”
message will appear. When you click on the button a Color Palette will open which
presents a Toolbar range of 5 palette options for selecting colors as illustrated.
26
1. The CODA Toolbars
There are 3 function features common to all the 5 palette choices which will assist you in
enhancing the coding of your CODA Form. The “magnifying glass” symbol at top left beside the
color bar can be used to capture a specific color hue from anywhere. By clicking on the symbol
it will become your cursor. Next place this modified cursor over the color you want to use and
click on it. The color chosen will be displayed in the color bar and if you have the target button
highlighted it will also change to the color choice.
At the bottom of the Color window is a row of boxes. These boxes may be used to store any
special or favorite color mixes you have chosen so that they may be recalled at any time. Once a
color has been chosen and that color is displayed in the color bar click on the color bar and drag
the color to one of the favorites boxes at the bottom of the color window. To recall a color simply
click on the color in the favorites box. Click on the small circle under the row of boxes and drag it
down to display further boxes if you need them.
Immediately above the line of Color favorites boxes is an Opacity slider. This may be used to vary
the opacity of a color selected and displayed in the color bar. The Opacity Slider can also be used
to make a button transparent for use in some more advanced coding applications.
You may color buttons in the CODA Form by highlighting the button then click on the “COLORS”
Icon and selecting your preferred color palette, then clicking on the color choice.
You may color the text of a button by highlighting the button, double clicking on the button
text, then following the instructions in the previous sentence. You may also wish to refer to para.
1.j (viii) above for options within the “Fill” submenu of the “Inspector” function to effect color
change.
l. Fonts
When you place the cursor arrow over the icon the “Show Font Panel” message will
appear. When you click on the Icon a drop down window will appear, which will
provide a full range of font options for your selection.
To change the font of any text in the CODA Form, highlight the button and
then click on the “FONTS” Icon. Select the font style, typeface and size from the
27
1. The CODA Toolbars
selections in the drop down menu. To change the text color in this menu routine click on the
color box and choose the color from the palette choice. For more detailed color options refer to
para. 1.k above.
m. Link Action Displays
The icons represent the “Outbound Action Links” (on the left) and the
“Inbound Action Links” (on the right). By default, for a button which has
no links, the “On Activate” and “On Deactivate” actions will be listed in the Outbound Action Links
display.
A link may perform multiple actions. Outbound links are
links which are initiated by either activating or deactivating
a code button. Inbound links will cause an action or actions
to be performed at a target or reciving code button as a
result of the link stimulus from an initiating source button.
Selecting either of these icons for an object will display the
actions that the link will perform in their sequential order
from top to bottom. You may change the sequence order
for Outbound Links by highlighting the action and dragging
and dropping it in your preferred position. Inbound Link
action sequence cannot be amended.
Delete a Link Action
To delete a link action, highlight the action and click the “X” symbol alongside it. The entire link
will be deleted when all the actions for the link have been deleted.
n. The Code Mode Toolbar
Click on “Code”to select the coding mode for CODA to operate in.
28
1. The CODA Toolbars
o. Saving and Retrieving your Work
If you have edited or added to your CODA Form the red button in the top left
hand corner of the Toolbar will indicate this by displaying a dot in its centre.
Click on this red button and the following window will drop down to confirm
your intentions.
Or you may select the “Save Last Coding Form As...” from “FILE” in the Main Menu. Saved CODA
Forms will be represented by this icon :
When you are in Code mode, and the “STOP” button is clicked a drop down window will seek
details to save the recorded information.
Using the relevant text box , name the file and also select the file address. We recommend that
you initially save it to your Desktop. You then need to select the Output Format you prefer.
If you are to use either the SportsCode™ or Studiocode™ applications the SportsCode XML
format selection is recommended. Files saved in XML format will be represented by this icon :
If you wish to export the data into Excel and then use this software application to sort the data
to provide other performance analysis reports you should select CSV. Files saved in CSV format
will be represented by this icon :
When the file is “Saved” the Event Log clock will stop and it will be reset to 0:00:00
Refer to para. 12 below for more detailed instruction regarding coding.
29
2. Button Resizing & Reshaping
p. Password Protection
You may place a password protection on a Code Form to either protect the form at opening or to
protect the design of the form from being altered after opening.
To place a password protection on your form, click on a blank area of the coding form then open
the Inspector. Input and verify your password, then select the option for where you want the
password protection to apply.
It is possible to retrieve the most recently saved CODA Form, but any changes you have made to
that CODA Form will be lost. To exercise this option, with the CODA Form open, select “FILE” then
select “Revert”.
30
2. Button Resizing & Reshaping
2. Button Resizing & Reshaping
To re-size a button click on the button to display the re-sizing knobs. By clicking on a corner
knob, you will anchor the button on the diagonally opposite corner and then you are able to
drag your selected knob in any direction to change the shape and size of the button.
If you want to change the size of a button, but keep the button dimensions in proportion to the
original button, (this is often needed when an image is used as a button,) click on a corner re-sizing
knob and then while holding down the “Shift” Key, drag the knob until you have the size you want.
The Slice Tool
The Slice Tool will not be accessible until an eligible button (Event, Popup Tag or
Tag) which has an image as a fill is highlighted.
With the button highlighted, click on the Slice Tool icon in the Toolbar. As you
move your cursor back to the Coding Form, the cursor will assume the shape of
a knife.
Move the cursor to the point on the button where you want the slice to start and click and hold
the mouse button down then move the knife in the direction of the slice - a straight red line will
be drawn from that point through the button in opposite directions. By moving your cursor tip
this line will rotate to indicate where the slice will occur. Move the cursor until you have the line
positioned where you want the slice to occur and then release the mouse button. The button
will be divided into 2 pieces along the axis of the slice. The buttons will appear as a multiple
selection. Deselect the multi-selection and reselect the individual button to assign individual
properties. Each piece will be a button with all the properties of the original, but the Appearance
Fill of each will be amended to the sliced image.
31
3. Getting Started
3. Getting Started
It is assumed that you have read and understood the information contained in the
preceding Chapters of this Manual before progressing to applying the functions of the
software tools to Coding.
Building a CODA Form
When you open CODA from the Dock or from the Application Icon on the Desktop the CODA
Window will open. This window will be blank if you have not selected to “Show Document
Startup Dialog” from the “Preferences” sub-menu in “CODA ” on the Main Menu bar. If this box
has been “checked” then you will see the following Startup Window on your screen.
OR :
To open a new CODA Window at any time, go to “FILE” then select “New Form”.
A Window becomes a Form when you start placing coding objects in it.
To open a CODA Form that has been saved, go to “FILE” then select “Open Form” and select the
CODA Form file address and the file name from the system menu. Alternatively, if the CODA Form
is one which has recently been open, select “FILE” then “Open Recent”. A drop down menu will
display a list of recently worked on CODA Forms, select the CODA Form you are seeking.
You may wish to clear the “Open Recent ” selection if you have deleted draft CODA Forms. To do
this, select the “Clear Menu” option.
If you are building a CODA Form with the intention that it may be used with an
iPhone or iPad, in either portrait or landscape format, you may have the bounds
of the screen real estate for these options displayed on your form as a reference.
Select your Show/Hide options from the “VIEW” dropdown in the Main Menu.
32
4. Creating and Specifying an Event
4. Creating and Specifying an Event
Select “EVENT” from the Toolbar to open/create an Event in the CODA Form. Click on the Event
in the CODA Form to identify it. It will become surrounded by re-sizing knobs to indicate that it is
selected and then go to the “INSPECTOR” icon on the Toolbar.
You should now name the event and also specify all the CODA Form parameters which the
Inspector function describes. Be sure to include the Event Time Tweaks details (refer to para. 1.j
(ii) above), to instruct the Sportstec Gamebreaker, SportsCode™ or Studiocode™ system what to
play when the event is selected for viewing. The Event Button data will be depicted as a Code
Row in a SportsCode or Studiocode timeline which will create a movie instance.
In the illustration below the activity is “Grading Fruit on a Conveyor Belt to remove over ripe fruit”
The Events created have been named to describe the 3 selection possibilities in this activity.
Reconfiguring an Event to a Tag
You may have created an Event and then subsequently decided that it would more appropriately
function as a Tag. To change an Event to a Tag , Control Click on the Event and from the drop
down menu select “Convert into Tag”. Consider the implications of this carefully because
reconfiguring the button to a Tag will cause the button to act merely as a label ie. it will not
create a movie instance.
33
5. Creating and Specifying a Popup Tag
5. Creating and Specifying a
Popup Tag
A Popup Tag cannot be created unless an Event is selected which the Popup Tag will be attached
to. Select the Event you wish to attribute a Popup Tag to by clicking on it and then click on the
“POPUP TAG” icon on the Toolbar. A Popup Tag will open in the CODA Form within a Popup Tag
Mat which surrounds the Popup Tag(s) and the Event it is attached to. An alternative method is
to select the Event , Control Click and select “Add Popup Tag” or select the Event and right click
and select “Add Popup Tag”
You should now name the Popup Tag to further describe an aspect of the Event by selecting the
“INSPECTOR” icon from the Toolbar. An abbreviated Inspector window will drop down. Name
the Popup Tag with the description you wish to attribute to the Event and all other CODA Form
properties such as button color, shape and border you want displayed and any Hot Key option
you may wish to specify.
A Popup Tag will be depicted as a label in the movie instance created by the Event button it is
attached to when the data is exported into either SportsCode or Studiocode.
The illustration below shows 3 Popup Tags created to describe the Event.
The Event signifies a Banana being selected from the grading conveyor belt and the
Popup Tags as further possible descriptions of the Event selection.
6. Creating and Specifying a Tag
You create a Tag by selecting the “TAG” icon from the Toolbar or Control Click on a blank part of
the Code Form and selecting “Add Tag”. The Tag is specified by using the “Inspector” window in
the same way as for Events and Popup Tags.
Tags may be assembled together into Tag Groups. Refer to para 1.j(v)
When CODA data is exported into either SportsCode or Studiocode, a Tag will be depicted as a
label in any or all movie instances created by any or all Event Buttons active at the time the Tag
Button is selected. When CODA is exported for Sportstec Gamebreaker, no Tag information will
be imported.
34
7. Importing an Image to the CODA Form
In the illustration below, the Tags have been given an elliptical shape as well as a distinctive
color. They are outside the Tag Button Mat and so they are independent of the Event but may still
be “attached” to it as a further description.
Reconfiguring Tag and Event buttons
You may have created a Tag and then subsequently decided that it would more appropriately
function as an Event or vica versa. To change a Tag to an Event , highlight the Tag and from the
“EDIT” menu select “Convert into Event”. You should note that the Shape, Color and Name given
to the Tag will not change with its change of function. These must be amended separately if
necessary.
You may also achieve this by highlighting the button and Control Click on it. Consider the
implications of this carefully because reconfiguring a Tag Button to an Event Button will change
the function of the button from describing an action in a movie instance, to initiating a movie
instance when the CODA data is exported into either SportsCode or Studiocode.
7. Importing an Image to the
CODA Form
Images you wish to import into the CODA Form must be in either pdf, gif or jpeg format. Any
image placed in a CODA Form will initially function as an Event button.
If an image has been selected from an external document, place your cursor at a corner of the
selected image and key “Command, Control, Shift and 4” and then click on the corner of the
image and drag the cursor to the diagonally opposite corner and release the mouse button
to capture the image to your desktop as a Screen shot. You may then either click and drag the
image from your desktop into the Coding Form and drop it or you may fill an existing button
with the image (refer paragraphs 1.j (vii) and 1.j (viii) above).
If your favored image has been stored in a file in your computer, it may be retrieved to the CODA
Form simply by clicking on the file name and dragging it to the Form.
The image may then be positioned anywhere in the CODA Form by clicking on it and dragging it
to the desired location. The image may also be re-sized or reshaped in accordance with details in
para.1.j (vii) above or by clicking on a corner and dragging the image to the desired size.
An image filled Event button, created in this way may also be re-configured to a Tag button
pursuant to the instructions detailed in para. 4 above.
35
8.Duplicating CODA Form Combinations
8.Duplicating CODA Form Combinations
If there are button combinations which you wish to duplicate, it is possible to
duplicate a button combination in the same CODA Form. There are 3 ways this
may be achieved.
1. Control Click on the Event button for the combination you wish to duplicate and from the
drop down menu select “Duplicate”. To move the duplicated button click on the centre of the
button and drag it to the desired location. It is not possible to duplicate a Button or Button
combination from one CODA Form to another CODA Form using this method.
2. Hold down the Command key and click on all the buttons in the combination. Then hold
down the Option key, click on the middle of the Event button and drag the combination to the
desired location. It is not possible to duplicate a Button or Button combination from one CODA
Form to another CODA Form using this method.
3. Use the Apple Keyboard Quick Key function by selecting the Event button for the button
combination you wish to duplicate then COMMAND+C and then COMMAND+V. This method can
be used to copy a button combination between CODA Forms.
Any Hotkey assigned to a button will not be duplicated. Links will also not be duplicated unless
the combination of linked buttons is duplicated.
36
Advanced Functions
Summary
Now you have a CODA Form for the hypothetical activity in which you have created 3 Events and
filled the Event buttons with the images for each. Each Eventbutton has 3 Popup Tags and 2 Tags.
You have grouped the Popup Tags by color, you have named them all to describe their various
event descriptors and possible outcomes; and the Tags, (which may be selected at random as
non-associated event descriptors,) are differentiated by a distinctive elliptical shape.
What has been described in paragraphs 4 – 8 above are the basic building blocks of the CODA
application.
As a starting point for your own activity it would be helpful to you if you were to compile a list of
all the primary events, (each of these will become an Event Button,) that may occur during the
activity.
Next, for each of these, list the variable descriptions which may arise. Those descriptors which
are specific to an event will become Popup Tags, those which are global to the whole activity will
become Tags.
In the example above, the primary events possible are the selections from the grading belt of
either a banana, a peach or a pineapple. A further possible description specific to each piece of
fruit, is that the piece of fruit selected may be unripe, it may be ripe or it may be over ripe. These
are the Popup Tags which are linked to each Event. A further consequence description which has
been added but would not necessarily be dependant in the event is that the piece of fruit could
be replaced on the grading belt or discarded. These 2 consequences are Tags.
37
Advanced Functions
Advanced Functions
You will appreciate that within your chosen activity, there will be that activity’s unique events
and possibly also a variety of unique resultant event permutations depending on how the
activity develops.
If you were to code every Event or Tag and the total number of resultant Event or Tag
permutations for each into a CODA Form, the size of the Form would have the potential to
be large; and the ability to rapidly find and activate and deactivate each Tag or Event with its
resultant Popup Tags and record them, (in real time,) could become impractical.
One solution to this is to have individual coding personnel coding a very focused facet of the
activity with a greatly simplified template. Another solution is to incorporate a mechanism
where code buttons can be automatically activated and/or deactivated in the CODA Form by
establishing links between selected buttons.
9. Links
A Link is used to automatically activate or deactivate buttons in a CODA Form as a consequence
of how the activity is unfolding. A link may also pass Tag information from a source Tag to a
target Event when the link activates or deactivates the target Event.
The benefit of using Links is to reduce the number of manual button activations and/or
deactivations, (clicks) that an operator would need to perform. The use of links in the Form will
make the coding of your activity more efficient.
Links can be initiated when an Event, Tag or Popup Tag button is activated (button clicked down)
or when an Event button is deactivated (button clicked up).
a. Link Protocols
A Link may be used to “activate” , “deactivate” or to “reactivate” a button.
A Link will not be activated unless the Source button is active.
A Link to a Tag button may tag or pass its tag as well as activate the button.
A link will only work in the direction of the link.
A link may be established
– from an Event button to another Event button or to a Tag button
– from a Tag button to an Event button or to another Tag button
– from a Popup Tag button to an Event button or to a Tag button
A Link cannot be established :
– from an Event button to a Popup Tag button
– from a Tag button to a Popup Tag button
– from a Popup Tag button to a Popup Tag button
38
9. Links
Terminology
An “On activation” link will perform when the source button (Event, Popup Tag or Tag) is
activated. An “On activation “ link originates from the source button icon
which is located on the left side of the button. An “On activation” link is
depicted on the Coding Form as a green link line.
An “On deactivation” link will perform when the source button (Event only) is deactivated. An
“On deactivation “ link originates from the source button icon which
is located on the right side of the button. An “On deactivation” link is
depicted on the Coding Form as a blue link line.
Note : It is important that the user understands that the terminology is in reference to the source
button not to what the link will do to the target button.
Establish a link
From a Source Button
1. Click on the Source button to highlight it. It will be backlit with a
purple hue, display the 8 resizing knobs and the On-activation
link icon on the left (in the case of Event, Tag and Popup Tag
buttons) and also the On-deactivation link icon on the right in
the case of Event buttons.
2. Click on the link type you want (link “On activation” or link “On
deactivation”) for your source button and drag it to the button
you want to link to (your target button).
3. An On-activation link from the source button will be shown as a
green arrow. An On-deactivation link from the source button will
be shown as a blue arrow.
To a Target Button
When you link a source Event button to a target Event button you have
the option to either “Activate” the target button or “Deactivate” it.
When you link a source Event button to a target Tag button, you
may only “Activate” it.
When you link a source Event button, Tag button or Popup
Tag button to a target Event button you have the six options
illustrated at right.
The “Reactivate Lag Time” option will only be visible if the target
Event button has a lag time property.
When you link a source Tag button to a target Tag button you have the option to “Activate and
Pass Tag” or to “Activate” only.
When you link a source Popup Tag button to a target Tag button you have the option to
“Activate” only.
39
9. Links
To display a links properties click on the link. The property(s) displayed will be in reference to the
button which is highlighted.
Remove a Link
To remove a link highlight the button and open the Inspector. Select the relevant
Inbound or Outbound Links icon then select and highlight the link from the
relevent (On Activate or On Deactivate) column and click the X icon in the row or
click on a displayed link and click the X in the link descriptor displayed.
b. Pass Tags
By default, a Tag button when activated will tag all active Event buttons. If the
Tag button is linked to another Tag button and the link instruction is “Activate
and Pass Tag”, then that Tag’s default setting to activate all active Event buttons
is automatically turned off and it will only activate and tag the target Tag button.
The Tags properties will be passed on to the linked button and will in turn be passed on to an
Event button(s). Note: For the Pass Tag instruction to be actioned, a chain of Tag buttons MUST
terminate in a link to an Event button.
Tags cannot be passed on from an Event button to another Event button.
c. Exclusive Link Cluster
A Link which is “Exclusive” between a grouping of buttons will occur when you know that two or
more separate events cannot occur at the same time. This is a useful tool where multiple Event
buttons which perform essentially the same marking function on the Event Log, (but which will
be mutually exclusive,) can be grouped together to ensure that when one of those grouped
buttons is active, no other button in that group can be active.
An example of this would be if a Basketball Court were to be divided up into 8 Zones and
the Basketball game was being coded so that play in each Zone was being tracked, then at
any instance in the game, play can only occur in one Zone. If Zones 1 – 8 were grouped in an
Exclusive Link, then when one Zone button is activated on the Event Log all other Zone buttons
could be de-activated. This would halve the number of button clicks which would be necessary
to code the activity.
To set up an Exclusive Link Cluster you must first identify which Event buttons in the CODA Form
will qualify as having mutually exclusive properties. Next click on one of the buttons and then
click on the “INSPECTOR” Icon. Hold down the “Command “ Key and click on each of the other
Event buttons selected as part of the Exclusive Link Cluster. Name the cluster in the text box
provided in the Inspector window.
40
9. Links
To identify which buttons in the CODA Form are members of an “Exclusive Link Cluster”, click and
hold on an Event button. If that button is a member of an “Exclusive Link Cluster” it will be backlit
by a rose colored hue and every other Event button which is a member of that cluster grouping
will also be backlit.
A button can only be assigned to one (1) Exclusive Link Cluster.
A further function restricted to members of an Exclusive Link Cluster is the ability to pass the last
Event code as a Tag ie. if an Event button is activated while another member of the Exclusive Link
Cluster is still active, the new Event will be activated and marked with the last Event as a Tag and
the last Event will be deactivated
To enable this function, select the “Pass Last Code as Tag” box for the Exclusive Link Cluster.
d. Putting the Links Together
In the example we have been using to illustrate creating components of our CODA Form, the
rules of the activity are that only 1 piece of fruit may be selected at a time; if the piece of fruit is
unripe it must be replaced on the conveyor belt and another piece of fruit selected; if it is over
ripe it must be discarded and another piece of fruit selected.
In our example now illustrated below we have created 12 links to substantially automate the
rules process described above and we show you the “on activation” links from the Tag button
“Replaced”.
The 3 Event buttons should be placed in an Exclusive Link Cluster because only one of them can
be active at any point in time.
An “On-activation Link” (with a green arrow) has been created from each of the “Unripe” Popup
Tag buttons to the “Replaced” Tag button. An “on activation Link” has also been created from the
“Over Ripe” Popup Tag buttons to the “Discarded” Tag button. 6 Links in total.
41
9. Links
An “On-activation Link” has been created from the “Replaced “Tag button to each of the Event
buttons with the target button instruction to “Tag and Deactivate”. Similar links have been
created from the “Discarded” Tag button to each of the Event buttons. 6 Links in total.
When the activity in this example is being coded, the coding operator observing the activity would
click on the Event that represents what has happened, (say … a Banana has been selected) and then
observed that the banana was over ripe, ( then clicked on the “Over Ripe” Popup Tag within the Popup
Tag Mat.)
The Exclusive Link Cluster which links the 3 Event buttons will prevent any of the buttons
associated with Peach and Pineapple from being activated until Banana becomes deactivated.
The “On-activation” link which exists between the “Over Ripe” Popup Tag and the “Discarded”
Tag will activate the “Discarded” Tag Button and then the “On-activation” link between the
“Discarded” Tag and the Event buttons with the instruction to “Tag and Deactivate” will ensure
that the “Banana” Event Button is first tagged with the tag “Discarded” and then it is deactivated.
This will eliminate the need for the operator to click on the “Discarded” button to activate it as
well as on the “Banana” button to deactivate the Event ie. in this instance it halves the required
operator coding activity.
To display what the functional status of a Link or Links to or from a button are, click on the
button, it will be backlit with a purple color, then open the “INSPECTOR”. Click on the “Outbound
Action Links” icon to display the “On Activate” and “On Deactivate” actions of the button. Click
on the “Inbound Action Link” icon to display the actions which will result from the inbound
activations.
e. Event Button Reactivation
Para. 1.j (ii) above details the functions set up by Event Time Tweaks and in particular the effect
that setting a Lag Time has on the period of time after the point at which the Event button is
activated until the Event button will be automatically deactivated.
If a target Event button has a lag time property, when a link is established to it
there will be an added “Reactivate Lag Time” instruction option. Reactivating the
button will restart the lag time counter and in the resultant timeline extend the
length of the instance by the period of the lag time. It will not create another event
marker on the Event Log.
An “Activate” instruction and will be ignored and the Event Log will not be marked if the target
button is already active, therefore a separate “Reactivate Lag Time” instruction link will be
required.
42
10. CODA Form Management
10. CODA Form Management
a. Arranging the Form in Layers
If the CODA Form you have built becomes large, it is possible that it will not fit within the
boundaries of your screen. This could cause a problem later when you are coding the activity. If
this is the case, it is possible to begin stacking buttons in the CODA Form in layers one behind or
one in front of the other. You may stack as many buttons as you wish.
The “ARRANGE” Menu allows you arrange a stack in what ever order you prefer. The arranging of
the order in an existing stack may also be done by Control Clicking on a button in the stack and
then selecting the option you want from the drop down Menu.
As you build and arrange your buttons in the CODA Form, you may lock a button in position in
the CODA Form by Control Clicking on the button and selecting “Lock Position” from the drop
down menu. It may be Unlocked in the same manner.
This feature is especially useful when you have arranged linked buttons in a stack and it is
desirable to maintain their position in the stack relative to one another.
The Popup Tags on a Popup Tag Mat in the CODA Form can be hidden and redisplayed by
Control Clicking on the Event and selecting “Hide/Show Popup Tags”
b.Transparent Buttons
In some instances, where a button will only be activated and deactivated by linking, or when a
button is being placed over a graphic in a stack, you may wish to make the button or series of
buttons transparent so that they do not clutter the coding Form. Refer to para. 1.j (viii) above for
instructions on how to make a button transparent.
43
11. Email a Form
c. The Container
The Container is a device which functions in a “popup” manner and which
contains coding objects. The primary function of the Container is for
organising the coding form to allow complex code forms to exist within
limited screen real estate. There may be containers within containers. A
container will act as a separate coding form.
coding objects within it.
Click on the Container icon in the toolbar to create a
Container in a coding form. By default a new container which
contains no coding form objects will be in its expanded state.
Use the circular symbol to collapse or expand the Container.
A container when selected (highlighted) will be backlit with a
purple hue. The container will resize itself to accomodate the
A Container will be activated (expanded) or deactivated (collapsed) by links from an Event,
Popup Tag or Tag button. Be mindful that if a Container is selected, any objects created will be
placed inside this container.
11. Email a Form
A form created in CODA may be emailed to an iCODA device.
A form must be saved before it can be mailed.
To add the form as an attachment to an email, click on the CODA icon at
the top of the form and drag it to the body of the email (or to the email icon in your dock) and
drop it. The recipient of the email will require iCODA or CODA to open it.
44
12. Coding an Activity
12. Coding an Activity
Once the SportsCode™ / Studiocode™ CODA Template / CODA Form has been completed you are
ready to begin coding an activity.
Click on the “Code” option on the CODA Toolbar to go to Code Mode.
You will be offered a window to save your design work. We strongly recommend that you save
your design work before you begin any coding activity.
The Coding Mode Toolbar illustrated below will appear and your CODA Form will be displayed in
“opaque” format. This means that the Form contents will not be available to mark events on the
Event Log until CODA is “Started”.
Note that no Popup Tag buttons will be displayed until the Event button they are associated with
is activated. Popup Tag buttons will also disappear when their Event button is deactivated.
The “Coding Time” display identifies the elapsed time timeline that the coded events will be
recorded against and it is also the reference point that will identify the coded events on the
Event Log to the video footage of the activity in the SportsCode™ / Studiocode™ video analysis
system.
In “greyed out” mode the buttons in the CODA Form are not active. They will become active once
the coding session is started by clicking on the “START” button. The “START” and “STOP” buttons
will start and stop the Event Log.
When you are coding an activity, a “Coding History” window will be displayed which will keep a
sequential record of the Events coded, the start and end time of when an Event is “active” and a
record of all tags activated which are associated with the recorded Events.
45
12. Coding an Activity
This window will sequentially record the Events which have been activated as they are activated,
(either from the User pressing the Event button or as a result of a Link,) and display if an Event is
still active. It will also record the start and end time on the timeline for each Event marked. You
may choose whether or not to display the Coding History window by clicking on VIEW in the
Main Menu and selecting “Show/Hide Coding History”.
The window will also record the information from each Tag and Popup Tag activated while the
Event is active.
You are able to Edit your coded information at any time before you stop your coding session
by using the Coding History window. If you highlight a selected Event, any Tag and Popup Tag
information attached to that Event will be displayed in the “Tags” window. You may delete (-) the
Event which will also delete any supplementary information attached to the Event; and you may
insert (+) an Event.
When you click the “+” button a list of Event buttons will be offered for your selection. You may
also attach Tag and Popup Tag information to your added event by clicking on the “+” button in
the “Tags” window and make a selection from the Tags offered.
You may also edit Tag history information in the same manner as Event history.
When the activity begins click on the “START” button on the Coding Toolbar.
The “Coding Time” display will begin recording the elapsed time. Code the events by clicking on
the relevant Event buttons to activate them. These will mark the Event Log with the Event. Also
record any Event descriptors set up as Popup Tags. Tags may also be activated which will add
further description to all Events which are currently active. An Event must be active for any of the
Popup Tag information to be captured. Any Links which have been included in your CODA Form
architecture will also influence what is being marked on the Event Log.
It will take a little practice to become proficient at coding an activity. A coding operator may wish
to alter some of the settings such as mat size and Time Lag as he/she becomes more familiar
with using CODA .
When your coding session is over, select the “STOP” button on the Coding Toolbar.
46
13. CODA Command Centre
13. CODA Command Centre
Linking CODA Desktop to iCODA, the Command Centre allows you to connect to an iCODA
application installed on an iPad , iPhone or iPod Touch; activate or deactivate the iCODA
application and transfer CODA Forms and Output Files. The Command Centre also allows you to
establish a CODA Server.
Note: The Command Centre will only link to iCODA and visa versa. iCODA is exclusive to iPhone,
iPad and iPod Touch. iCODA must be activated by a Command Centre license before it can be
used. Files from an activated iCODA may be shared with any licensed Command Centre.
To open the Command Centre window, click on
the toolbar icon in the toolbar.
The Command Centre window has 2 Mode displays - Devices & Server.
In Devices mode you establish and manage the mobile devices which are linked to your CODA
licence. The panel on the left side of the window consists of two sections - ACTIVATIONS and
DEVICES.
The ACTIVATIONS section contains the iCODA activation licenses which are currently available
to you. Activations may be issued with or without an expiry date. But, by default, an iCODA
activation with no expiry date will expire when the license period issued for the host CODA
application expires. When an iCODA licence is activated, the CODA licensee will nominate what
activation expiry date (if any) to allocate. The activations which are allocated at the moment
are displayed in orange. A green display indicates available activations that can be allocated for
new iCODA devices. If there are new activations which are not displayed in the section, press the
Refresh button to synchronize the list with the Sportstec server. You must be connected to the
internet for this operation.
The DEVICES section will display all the devices that have iCODA installed and which are
connected to your network. You may update your list displays at any time by clicking the Refresh
button
47
13. CODA Command Centre
Activate iCODA for a Mobile Device
There are 2 ways to activate iCODA for a mobile device to connect it to your CODA application
through the Command Centre. The first is for devices which are connected to your WiFi network,
and the second is for devices which are remote.
To Allocate an iCODA Activation for a Mobile Device Connected to your WiFi
Network
When CODA detects a mobile device in it’s network, this device will be be listed in the DEVICES
section at the left of the page. All the iCODA Activations which are linked to the CODA License
will be listed in the ACTIVATIONS section. The iCODA activations which are available for
allocation to a mobile device will be colored green. Any licenses which are already allocated will
be colored orange.
To allocate an iCODA activation to a listed mobile device, click on the device to highlight it. A
pinwheel will display while waiting for the device to respond to a connecting request. The
mobile device will then display a message to alert the device User that the Command Centre is
requesting connection. (See the illustration in the iCODA section on page 70)
Once the Device User has accepted or “Allowed” the request, select the activation you wish to
allocate (with or without an expiry date) and Click the “Activate” button.
One of the activation icons will turn orange to indicate that it has
been allocated. The iCODA activation is able to be used at this point
but it will not nominate who the User is .
48
13. CODA Command Centre
To name the Device User, the device must logout of and relaunch iCODA. Then in your Command
Centre click the Refresh button and the Device name will be displayed.
To Deactivate an iCODA Activation from a Mobile Device Connected to your
WiFi Network
To deactivate an iCODA activation in use by a mobile device which is connected to your WiFi
network, click on the device name in the DEVICES list to highlight it. In the right hand side, click
on the “Activation” button and then click the “Deactivate” button. This will reclaim the Activation
License so that you will be able to assign it to another device.
xxxxxxxxxxxxxxxxxxxx
To Allocate an iCODA Activation for a Mobile Device which is Remote from
your WiFi Network
The computer hosting the CODA Command Centre and the Mobile Device. must be able to
communicate in order to convey the “iCODA ID” for the Command Centre to input. To allocate
an iCODA Activation to a remote device, the device must first send its iCODA ID to the CODA
Command Centre, either by email, SMS or other means.
In the Command Centre, click on an available (colored green) iCODA activation from the
ACTIVATIONS list to select it. The iCODA Activation screen will open in the right hand side.
49
13. CODA Command Centre
Copy the iCODA ID from the email received from the Device User into the iCODA ID Field. ( Refer
to the iCODA Manual on page 70 for procedure instructions )
You may also enter any comments in the free text field. These comments will be displayed with
the User information when you click on an allocated iCODA activation.
Click the “Activate” button.
The highlighted Activation icon will turn orange to indicate that it has been allocated and
activated. It is able to be used at this point but it will not display who the Device User is.
To display the Device User in the Activations list, the device must logout of and relaunch iCODA.
Next, in your Command Centre, click the Refresh button and the Device User will be displayed.
To Deactivate an iCODA Activation from a Remote Mobile Device
To deactivate an iCODA activation in use by a mobile device which is not connected to your WiFi
network, click on the device name in the ACTIVATIONS list to highlight it. In the right hand side,
click on the “Deactivate” button. This will reclaim the Activation allocated so that you will be able
to assign it to another device.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
50
13. CODA Command Centre
Working in the Command Centre
After the device has been successfully activated, the Activation tab view will contain information
about the used for the device.
The panel on the right of the Mobile mode window will display all the files stored on the active
mobile device selected in the left hand panel. See the illustration below. These file lists will be
empty if you have just activated your new iCODA application. They will contain all output files
created once coding sessions have finished on the device. The output files can be downloaded
to CODA and may be deleted from the device.
The file list in the Documents Panel contains CODA documents stored in the device. You can
download and delete files from the device and upload new documents onto the device.
Download Files from a Device
Select one or more files in the list. (Use the Shift or Command button for
multiple selection.)
Click the Download button from the panel at the base of the window and specify the
destination folder. Alternatively you can drag-and-drop the files onto the desktop or to
any folder in Finder.
To remove files from the device
Select files.
Click the Delete button from the panel at the base of the window.
Upload Forms to a Device.
Click the Upload button on the panel at the base of the window. Select the files
from your file source and press “Open” . Alternatively you can drag-and-drop files
from your Documents file list to the Command Centre panel.
51
14. The CODA Server
14. The CODA Server
The CODA Server is a feature that allows any number of CODA and/or iCODA applications to
participate in a synchronized coding session simultaneously and live via the internet. The basic
premise of this feature is that there must be a common receptacle for the coded information. The
Coda Server must be established through the CODA Command Centre to perform this task.
NOTE: By implication, online coding with CODA linked to SportsCode or Studiocode is a remote
application. IT consultation will be a must if you intend to use any IP address or Port which differs
from those which will appear as default settings. This may require a high level of network experience
and may be a very involved setup. Please contact your IT consultant or Sportstec for more information
or assistance.
Coding via a CODA Server will be available to any CODA and/or iCODA application. ie. It is not
restricted to licenses or iCODA activations linked to the CODA Command Centre which has
established the CODA Server.
A CODA Server has the capacity to execute multiple coding sessions at the same time from any
number of CODA and/or iCODA applications. In the Command Centre which has “hosted” the
active CODA Server, the number of active sessions are displayed as well as the participants to
each session who are currently connected or who have been connected and are now
disconnected. The number of events coded for each participant is also recorded.
Establishing a CODA Server
Select the “Server” Mode on the left of the Command Centre Toolbar.
In the panel at the top of the screen, specify a name for the Server.
The IP address for the server computer specified is a default. If you need to allow access to
another device from outside the LAN to send data to or to pull data from, it will be particularly
important that you specify a Public IP address. We strongly recommend you consult with your IT
Manager.
52
15. Network Coding
By default, Port 8080 is specified. If that port is in use, you will get an error message
“ The port for this IP address is already in use” You will be required to either stop the service
which is using that port, or select another port.
The “Sessions Root Folder” is the file path for the root folder of where the system will store the
coding session timelines. CODA will specify a default file path culminating in the file named
“Coda Sessions” . By default, this folder location is shared. Ensure that the “File Sharing” box in
your System Preferences is checked (turned on).
Slide the switch to ON to activate the CODA Server.
If you change the folder location to another path, folder sharing should be turned on for the
Folder location chosen, so other computers in your network can access the coding session
timelines.
1.
2.
3.
4.
5.
6.
In Finder, navigate to the chosen sessions root folder
Right Click on the folder
Select “Get Info”
Check the “Shared Folder” box
Select either “Read & write” or “Read Only”
Click on “Start Server”
Once the CODA Server is running, (the Status field will display “Running”) the above fields cannot
be edited.
If there are no sessions active, the server may be stopped by clicking the “Stop Server” button.
If there is a session active and you attempt to stop the Server, you will receive the following
message: “Close all sessions and STOP CODA Server” The “Stop Server Now” button will force all
sessions to close and the server will become inactive. All connected devices will show that the
session has been disconnected. That device will not be able to reconnect because there will no
longer be a server to connect to. All data captured by the server to that point will be preserved.
The session may also be closed by the server at any time by pressing the “Close Session Now”
button.
53
15. Network Coding
15. Network Coding
Network Coding is a feature that allows any number of CODA and/or iCODA applications to
participate in a synchronized coding session simultaneously and live via the internet. The CODA
XML data file which is created from the multiple coding inputs is available to be pulled into
SportsCode or Studiocode in real time.
With Network Coding you will “share” a common Timeline in a Coding Session that is hosted on
a CODA Server so that multiple coders can input coding of an Event simultaneously. You will be
using the Coding Form through which you accessed the Network facility, so be very sure that
you have selected the correct form relevant for the Coding Session.
You will be required to be connected to a CODA Server to participate in a Network Coding
Session. Refer to the CODA Server section of this Manual for a description of the CODA Server
setup.
Slide the “Network” switch in the Code Mode toolbar to the right (ON). A sheet will display. In the
upper panel of the sheet, the names of the servers in your LAN only which are available to you.
The names of the servers which are not available in your LAN which you have previously
connected to using the “Other Server” button will be displayed in the lower panel.
If this is the first time you have logged into a CODA server the above sheet will be blank.
The image above illustrates that the window will have a “greyed out” appearance until the
Network Coding session has been started.
a. Connecting to a Server
To connect to a server which you have not previously connected to, (either within
your LAN or externally), or if this is the first time you are connecting to any CODA
Server, click the “Other Server” button at the bottom left of the sheet illustrated
on the previous page. You will be presented with the following sheet to provide the Name, IP
Address and Port details of the external Server or new Server you wish to connect to.
54
15. Network Coding
These details should be provided to you by whoever has established the Server. If any details are
incorrect you will get a “Connection Failed” message.
Once you have established a Server connection either by selecting and clicking on the Server
name from the Server list or by connecting to a new Server, select the Session (by Session Name
displayed,) or you may create a new Session.
b. Creating a New Session
From the “Session List” click the “New Session” option. The device which creates a new session
will become the owner of the session and will be required to start the session.
It is mandatory when creating a session to provide a session name. You may also choose to
establish a password, without which other participants may not join the session.
Click “Create” to create the session. If the session is successfully created, you will be taken
directly to your Coding Form in the Code Mode screen where CODA will wait for you to Start the
session.
55
15. Network Coding
c. Connect to (Join) or Reconnect to a Session
From the Session List panel, highlight the session you wish to join and click the
“Join” button. If a password is required, input the password and click “Join”. If the
password is correct, you will join the session and you will be taken directly to the
Coding Form in your Code Mode. Turn the Network switch ON. There is an
Connection status indicator located next to the switch which indicates that you are
connected to the server if it is green. When the connection is broken it turns red.
If the session has not been “Started”, the Code Mode screen will be “greyed out” which will
prevent you from activating any code button(s), but you will still be connected to the session.
The Coding Timer will show 0:00:00 to confirm that the session has not started. Once the session
is started, the Coding screen will become “clear” and the Coding Timer will be counting.
d. The Coding Session
The coding session may be joined by any number of participants. Access to a session may be
restricted to participants by password. A participant may join and/or leave a session at any time
between when a session is created and when it is stopped.
When a participant joins a session after a coding session has been started, the participants
coding timer will display the time elapsed from the start of the coding session (not from the time
the participant joined the session).
The session will be stopped on the CODA Server only when the last participant disconnects.
56
15. Network Coding
e. The Session Owner
The person/device which creates a session is the “Owner” of the session. The key function which
the owner must perform is to “Start” a coding session. No other participant is able to start a
session.
f. Start Coding
Once the session owner has started the session, the Code Mode screen will become clear and
you may begin coding. If the session is in progress when you join, the Code Mode screen will be
clear and immediately available for coding.
g. Session Timer and Synchronization
Once a session has been started, all the session participants, (including the Session Owner),
become equal participants as far as the CODA server is concerned. In the toolbar of a
participants coding screen a Coding Timer displays the server time elapsed since the session was
started. All participants will display the time elapsed since the start of the session irrespective of
when they joined the session. This ensures that the coding from all participants is synchronized
with a common timeline.
Note: It is conceivable that an event could be coded live from devices located in varying time
zones. In such an instance, CODA uses UTC as a reference time. (UTC is Coordinated Universal
Time which replaced Greenwich Mean Time {GMT} as the world standard time. For CODA
purposes, UTC and GMT may be considered as being the same). For synchronization purposes,
the CODA server is concerned only with time synchronization between itself and all the session
participants. If there is to be any third party application pulling the timeline data from the CODA
server they must ensure that these computers are also synchronized with their network time.
57
16. Exporting your Coded Data
h. Disconnect from / Stop a Session
You may deliberately disconnect from the session at any time by clicking the “Stop” icon button
in the Code Mode toolbar. If the Online Coding status indicator which is located on the Coding
Session Timer changes from green to red during an online coding session, this indicates that the
connection to the server has been broken. CODA will automatically attempt to re-establish the
connection.
A disconnection which is not deliberate will not affect your coding records because CODA saves
your coding data at your device and sends it to the server at intervals. CODA records what data
has been transmitted to and saved by the server and as soon as the reconnection is established,
CODA will “catch up” on the data coded during the period of disconnection.
i. Data Transfer and Storage
CODA stores the data coded by each device on that device and it also transmits the stored data
at intervals to the CODA Server. If the connection between the device and the server is broken
during the session and it is unable to be restored, CODA will show the following message alert. It
is recommended that you retain the complete timeline file after you have been disconnected
from the server.
58
16. Exporting your Coded Data
16. Exporting your Coded Data
Interpreting CODA Event Log Data
CODA is designed to be used in conjunction with the SportsCode™ / Studiocode™ Analysis
products. For details of how to import the CODA Event Log into these products and for
information on how to manipulate the resultant data please refer to the relevant SportsCode™ /
Studiocode™ User Manual.
The data captured by CODA may be saved in either of the following formats:
-
XML document
Saved and exported XML documents are represented by this icon :
CSV Comma Separated Values. Saved and exported CSV documents are represented by
this icon :
Sportstec / SportsCode Timeline. Saved and exported Timeline documents are
represented by this icon :
Refer to Para. 1.n above for details.
Manipulating CODA Event Log data saved in XML format
The SportsCode™ / Studiocode™ applications will only accept import data in .xml format. Refer to
the relevant User Manual(s) for instructions.
Data captured in CODA and exported in .xml format is termed an “XML Edit List.” When this Edit
List is imported into either SportsCode or Studiocode it will be linked and synchronised to video
of the performance coded and the coded information will be in a timeline. The information
coded by Event Buttons will be depicted as a Code Row in the timeline, (which will create movie
instances,) and all Popup Tag and Tag information will be depicted as labels for each instance.
The information may be displayed as a Code Matrix and will be available for analysis in the same
way as information coded directly by the SportsCode or Studiocode software.
Note : Data imported from CODA can not be displayed in color in a SportsCode or Studiocode
Code Matrix.
Manipulating CODA Event Log data saved in CSV format
Double click on the .csv file on the Desktop or open it from where it has been saved to. The .csv
will open in Excel format. It will be tabulated in columns in event order. The data will now be
available to be sorted by column and in whatever order you choose to provide you with specific
activity information that will assist you in reviewing performance.
59
Appendices
(i) Keyboard Quick Key Functions
MENU ITEM – FUNCTION
KEYSTROKE
COMMAND
CONTROL
OPTION
SHIFT
LEFT RIGHT ARROWS
CLICK
FILE
New
N
Open
O
Close
W
Save
S
Save as
S
Page Setup
Print
P
P
EDIT
Undo
Z
Redo
Z
Cut
X
Copy
C
Paste
V
Select All
A
Copy Style
C
Paste Style
V
Special Characters
T
WINDOW
Minimize
60
M
(i) Keyboard Quick Key Functions
ARRANGE
Bring Forward
Send Backward
Bring to Front
Send to Back
Lock Position
L
Unlock Position
U
VIEW
Show Fonts
T
Show Colors
C
Show Inspector
I
Show All Hot Keys
K
Show Coding History
H
Hide Popup Tags
E
CODA
Preferences
,
C
Command Centre
Hide CODA
H
Hide Others
Quit CODA
H
Q
MAC OS X
Selection snap shot to memory
61
4 V to paste to
another window
(ii) Glossary of Terms
(ii) Glossary of Terms
Main Coding objects
Code button - A visual object represented by a particular shape or image.
Properties:
Code Name
Functions:
can be pushed down,
can affect the coding process,
can be the initiator for a link
Event - a code button
Properties:
Lead Time
Lag Time
Functions:
can become turned on creating a new instance
can become turned off ending the instance
can be the master of popup tags
can be the target of a link
Tag - a code button
Properties:
Global Tag
Functions:
label an instance
be the target of a link
Popup tag - a code button
labels its master’s Event instances
Link - an object that connects two code buttons
Properties:
Activate Target On Activation
Deactivate Target On Activation
Reactivate Lag Time On Activation
Activate Target On Deactivation
Deactivate Target On Deactivation
Pass Tags
Functions:
can turn a target on
can turn a target off
can reactivate a target’s lag time
can pass tag data
62
(ii) Glossary of Terms
Exclusive link cluster - A logical group that includes member events
Properties:
Pass Last Event’s Code
Functions:
turns members off
can pass the last Event’s code on to the next activated member
Other objects and terms
Instance - A passage in time, created by a particular event
Properties:
Start Time
End Time
Code Name
Labels
Active instance
An instance that has been created, but has not been closed yet. It has an empty End Time
property.
Current instance
An instance that is the last created with the event. When the coding session begins no Event has
current instance. The last created active instance is the current instance for it’s Event. When the
active instance is closed it remains the current instance until a new one is created.
Master event
An Event against its popup tags.
Coding session
A time interval that contains instances. A coding session has it’s own timer which starts with 0.
Code stack
An array of codes passed down a Link chain.
To label
Means to add a code name into the labels property of an instance.
Last Active Event
The last activated Event in the coding history. Even if it has been turned off (by run out lag time
or user action) it remains the Last Active Event. It is able to receive doLabel messages from tags
and links. Receiving doLabel messages makes it send doLabel messages to its current instance.
Messages
During a coding session the user sends messages to code buttons. Thereafter, the code buttons
send messages to the links connected to them.
63
(ii) Glossary of Terms
Code buttons can receive messages:
pushDown - the message is initiated when the user presses a code button.
doActivate - the message is initiated by a link.
doDeactivate - the message is initiated by a link or exclusive link cluster.
doReactivateLagTime - the message is initiated by a link.
doLabel - the message is initiated by a link or tag. This message contains a code stack.
Links can receive messages from initiator code buttons
initiatorDidTurnOn - the message is initiated by a code button
initiatorDidTurnOff - the message is initiated by a code button
doLabel - the message is initiated by a tag (initiator). This message contains a code stack.
Coding sequence
When coding objects receive messages they do the following actions in the following order:
Turned off Event receives pushDown or doActivate message:
Sends a initiatorDidTurnOn message to all outbound links.
Sends a initiatorDidTurnOn message to the exclusive link cluster.
Creates the active instance.
Turned on Event receives doActivate message
No actions
Turned on Event receives pushDown or doDeactivate message:
Sends a initiatorDidTurnOff message to all outbound links.
Closes the active instance.
Event receives doLabel message:
If the event is turned on or the event is turned off and is the Last Active Event it will label its current
instance. This means the event adds a code stack into the instance’s labels array keeping the order
of appearance.
Global Tag is pushed down by the User:
Sends a initiatorDidTurnOn message to all outgoing links.
Sends a doLabel message to all turned on events. The Code stack contains the tag’s code.
Tag is pushed down by the User:
Sends a initiatorDidTurnOn message to all outgoing links.
Creates a code stack and adds its code to it.
Sends a doLabel message with a copy of the code stack to all outgoing links.
Tag receives a doLabel message:
Adds its code to the received code stack if the code stack does not contain the tag’s code yet.
Sends a copy of the code stack to all outgoing links.
64
(ii) Glossary of Terms
Popup tag receives a pushDown message:
Creates a code stack and adds its code to it.
Sends a doLabel message to its master event.
Sends a initiatorDidTurnOn message to all outgoing links.
Link receives a initiatorDidTurnOn message
If the Activate Target On Activate property is set on the link sends a doActivate message to its
target.
If the Deactivate Target On Activate property is set on the link sends a doDeactivate event to its
target
If the Reactivate Lag Time On Activate property is set on the link sends a doReactivateLagTime
message to the target event.
Link receives a initiatorDidTurnOff message
If the Activate Target On Deactivate property is set on the link sends a doActivate message to its
target.
If the Deactivate Target On Deactivate property is set on the link sends a doDeactivate event to
its target
Link receives a doLabel message
If the Pass Tags property is set on the link passes a doLabel message to its target.
Exclusive link cluster receives a initiatorDidTurnOn message
Sends a doDeactivate message to all members except the initiator.
If the property Pass Last Code as Tag is set on the cluster sends a doLabel to the initiator. A Code
stack contains code of the previous event.
Coding routines
Creation of an instance
An instance can only be created by an event.
An Event creates an instance when it goes from a turned off into a turned on state.
An Event sets a Code Name of the newly created instance to be equal to the Event’s Code Name.
A Start Time is assigned at the moment of creation.
A Start Time is calculated using this formula:
Start Time = Current Coding Session Time - Lead Time
If the Start Time is negative it sets to be 0.
Closing of an instance
An instance can only be closed by the same event it has been created by.
An Event closes an instance when it goes from a turned off into a turned on state.
An End Time is assigned at the moment of closing.
An End Time is calculated using this formula:
End Time = Current Coding Session Time + Lag Time
65
(ii) Glossary of Terms
66
SPORTSTEC
iCODA
User Manual
iCODA Preface
iCODA Preface
iCODA is an application exclusive to the Apple iPhone, iPad and iPod Touch. iCODA will link
to the CODA Command Centre and vica versa. iCODA will also link directly with SportsCode
and Sportstec Gamebreaker for Timeline exports. This manual describes the principles and
techniques you need when using iCODA. For a more detailed description of CODA functions,
consult the CODA User Manual.
ICODA supports the operating Sysytem for iPhone 3GS, iPhone4, iPod Touch and iPad. iCoda
supports the following screen resolutions:
320 x 480 ppi (iPhone 3GS, iPhone 3G)
640 x 960 ppi (iPhone 4, iPhone 4S)
768 x 1024 ppi (iPad)
iCODA supports portrait and landscape screen orientation & auto orientation rotation.
Your iCODA application is downloadable from the iTunes App Store. The application must be
activated by a CODA Command Centre license before it can be used as an iCODA device.
Once an iCODA device has been activated by its host CODA application, it is able to be linked to
any licensed CODA Command Centre and to share Forms and Timeline files.
For a detailed description of the coding process please refer to the CODA manual.
Current iCODA Version
The current version of iCODA which this Manual applies to is Version 2.0.0
68
Linking iCODA to a Command Centre
Linking iCODA to a Command Centre
Once you have downloaded your iCODA application from the Apple Store it will operate in
Demo mode. In demo mode iCODA will function normally, but it will need to be linked to a
CODA Command Centre to perform the Command Centre functions of Online Coding and data
transfer.
You may link iCODA either by being connected to the WiFi network of the host CODA Command
Centre or remotely if you are not connected to the host WiFi network.
Your iCODA application contains a unique “iCODA ID” for you to link to a CODA License. You will
be unable to perform any Command Centre functions until your iCODA has been linked to a
CODA Command Centre.
Activation in a WiFi Network
When your mobile device connects to the WiFi network
of the host CODA Command Centre, CODA will detect the
device, read it’s iCODA ID and display your connection in
it’s DEVICES list.
When the Command Centre starts the linking process
for your device, your device will display the message
illustrated on the left.
If you tap “Allow this time only” the Command Centre ia
able to link your iCODA application with one of it’s licenses,
but as soon as you close your iCODA application, the link
will cease and in the future, you will be required to have
your application relinked next time you want to use it.
If you tap “Allow forever” the Command Centre will link
your iCODA application with one of it’s licenses and in
the future, both the Command Centre and the device will
recognise each other whenever the device is connected to
the WiFi network.
If you tap “Reject” the Command Centre will be unable to link your iCODA application this time.
Once your iCODA application has been linked from the host CODA Command Centre, you should
quit the application and relaunch it. This will ensure your device is identifiable in the Command
Centre by your device name.
69
Linking iCODA to a Command Centre
Remote Activation
The computer hosting the CODA Command Centre
and the Mobile Device. must be able to communicate
in order to convey the iCODA ID for the Command
Centre to input. To link an iCODA license in the
Command Centre to a remote device, the device
must first send its iCODA ID to the CODA Command
Centre, either by email, SMS or other means.
Tap the “clip” graphic of the clipboard to expose a
window that provides information about the iCODA
software version and also the iCODA ID which is
unique to each iCODA device.
To send the iCODA ID to a Command Centre, double tap the iCODA ID to highlight it and to
activate the “Copy” tab, then tap “Copy.”
Next close iCODA and open either your SMS message application or email. Select the address of
the CODA Command Centre and tap and hold in the text field.
From the options presented select “Paste”.
Once the email has been sent an email confirmation
message is displayed.
Once your iCODA application has been linked to the host CODA Command Centre, you should
quit the application and relaunch it. This will ensure your device is identifiable in the Command
Centre by your device name.
70
Navigation between iCODA screens
Navigation between iCODA screens
In the iCODA application there are 4 Operating Modes. These are the List Mode (Lists Forms or
Timelines) ; Design Mode (which includes the Inspector window) ; Code Mode and Timeline
Share (Email a Timeline). You can navigate between them at any time by using the relevant
navigation bar at the top of the screen, or by using the tab bar at the bottom of the screen.
(L to R) List Mode ; Design Mode ; Code Mode ; Timeline Share
In List Mode, you may “flip” between Forms and Timelines.
t From the Timelines screen you may “flip” to Forms or you may navigate to the Send Email
function.
t From the Forms screen you may “flip” to Timelines or you may navigate to Design mode and
to Code mode.
In Design Mode you may navigate to the Inspector functions and to Code Mode.
In Code Mode you may navigate to the Forms screen in List Mode , to Design Mode and to
Online Coding.
In Design and Code Mode, for a Coding Form which has been
uploaded from a Coda Command Centre (refer to page 50 of
the CODA Manual) and the dimensions of which are larger
than the screen size, the form display will be scrollable in the
X and Y axis. There is also a bar display at the bottom and right
of the screen to display what proportion and which part of the
form is displayed on the screen.
When you Stop & Save a coding session you will be returned
to List Mode.
71
Gestures
Gestures
iCODA employs the following gestures: single tap, slide, double tap, resize. Each of these
gestures performs a particular action on the target object.
Single tap
The single tap gesture is what you use to select buttons. It is performed by tapping an object
once without moving your finger before you release it.
In Design mode a single tap is used to select an object allowing you to “arrange” links etc. in
Code mode use a single tap to activate/deactivate coding objects.
Slide
The slide gesture begins by placing your finger on the target object, the finger slides into
another location and then is released.
Use the slide gesture to move an object on the screen in Design mode or to delete a Form or
Timeline in List mode.
Double tap
The double tap is a gesture that consists of two single taps, one after the other.
Use double tap to open the Inspector view for an object in Design mode.
Resize
The resize gesture is performed with two fingers touching the screen when at least one of them
slides.
Use this gesture to change the bounds of the selected object. The bounds of the selected object
will follow the fingers.
An object must not be locked to be moved with slide or resized with the resize gesture.
72
Objects
Objects
The following objects can be created in iCODA.
See CODA Principles in the CODA manual for a detailed description of the objects and the coding process.
Event Button
An Event Button is a coding object that opens and marks the log of Events in the Edit List when it
is activated and closes the log after it has been deactivated.
An Event Button can be both the initiator and target of a Link.
Popup Tag Button
A Popup Tag Button is a tag (see below) that is exclusively linked to its target Event. It appears in
the screen on the Popup tag mat only when its target Event is active.
A Popup Tag Button can be the initiator of a Link only to an object outside of its Popup tag mat.
Tag Button
A Tag Button is a coding object that is able to place a description into instances in the timeline.
A Tag can mark instances in two ways: by activating outbound Links and passing its tag
information down the Link chain or by marking all open instances. A Tag Button can be both the
initiator and the target of a Link.
Shape Button
A Shape is a decorative graphical object that helps you to create your visual scene on the coding
form. It can be turned into any picture you need, like any code button.
However, a Shape is not a coding object, ie. it cannot affect the coding process.
Text Box
A Text box is a decorative object that allows you to create an artistic text on the Form.
A Text Box is not a coding object, ie. it cannot affect the coding process.
Link
A Link is a coding object that links a source with a target. This means that a Link has direction
which is one way only. A link may be initiated when a source button is activated or when
the source button is deactivated. Depending on the defined properties, a Link can activate
or deactivate its target code button, reactivate lag time of a target event and/or pass tag
information from the source to the target.
73
Objects
Container
A Container is a form object. It behaves in the same way as a Coding Form and thus becomes a
Form within the Form (but it will have no name). Containers may be placed within containers.
The purpose of a Container is to manage the available screen real estate for your coding form.
Counter
A Counter is a dynamic graphical object which is linked to an Event or a Tag button. It will display
one of three options.
Slice Tool
The Slice Tool will only be available for use when an Event, Popup Tag or Tag button, which has
an image filling it, has been selected. The purpose of the tool is to provide a mechanismwhere
a button, which has an image filling it, can be separatedinto the component parts of the image,
with each part of the image becoming a button which will possess the same properties as the
original.
74
List Mode
List Mode
In List Mode you may “flip” between Forms and Timeline Lists by tapping the relevant tab in the
tab bar at the bottom of the screen.
The Forms List contains all the coding Forms previously created in
iCODA or uploaded from CODA using the Command Centre function.
(Refer to page 50 of the CODA User Manual) Importing Forms into
iCODA cannot be initiated by iCODA. The Form Name is preceded by a
thumbnail picture of the form.
The Timeline List contains all the Timelines previously created in
iCODA when you stop and save a Coding session. The Timeline Name
is preceded by the Timeline icon.
In List mode you can open an existing Form or create a new one. You
may also remove or change the name of a Form or Timeline.
Open a Form
To begin working with a Form just select
it in the list by a single tap. By default the
screen will slide to the right and open in Code mode. To change the form to Design mode, tap
the Design button.
Create a new Form
To create a new Form tap the Add button, (the +
sign,) in the upper-right corner. Type the new Form
name in the opened dialog box and tap the Done
button. The screen will then slide to the right going
directly to the Design mode.
75
List Mode
Password Protection
You may place a password protection on a Code Form to either
protect the form at opening or to protect the design of the form
from being altered after opening.
To place a password protection on your form, click on a blank
area of the coding form then open the Inspector. Input and verify
your password, then select the option for where you want the
password protection to apply
Remove a Form or a Timeline
If you want to delete a Form or Timeline, tap the Edit
button in the upper-left corner The list will switch to Edit
mode. Tap the delete mark on the left side of the List and
press the Delete button which will appear.
The Lists in Edit mode
Alternatively, to delete a Form or Timeline right from the List
without entering into Edit mode, you can tap the Form or
Timeline name and slide it sideways, (either left or right,) to make
the Delete button appear.
Warning! You cannot undo deletion of a Form or Timeline.
76
List Mode
Edit a Form Name or Timeline Name
Tap the Edit button in the upper-right of the Form or
Timeline List to switch the List to Edit mode.
Tap the Form or Timeline name to make the Rename dialog screen appear.
Rename the Form or Timeline..
Tap the “Done” button or “return” button to accept
the changes.
The Rename Form screen
77
List Mode
Receive a Form by Email
Forms attached to emails can be opened and stored in iCODA.
Select the attachment (tap the attachment or swipe
the arrow to the right), if iCODA is installed a popup
menu will appear with the option to “Open in iCoda”
or to Cancel.
Upon opening, the form attachment will
automatically be copied into the iCODA Form List.
However, if a form with the same name already exists,
you will be offered the options to overwrite the
existing form, rename the received form or cancel
the Open instruction.
Note: If you are engaged in an active coding session
and you choose to open an email which contains a form
attachment, in order to avoid losing coding data, iCODA
will not open the form but will save it to the Form List. If
the form attachment has a name which already exists in
the Form List, then the new form will be renamed with a
sequentially numeric suffix.
78
Design Mode
Design Mode
Design mode allows you to modify your Form both when a coding session has not been started
and during the active coding session. Within Design Mode you will find the Inspector window
which will allow you to modify properties of the Code window objects.
Warning: If you decide to modify a Form during a coding session, you should be careful.
Changing or removing any coding objects that have already been used in the timeline may lead
to data inconsistency. This may happen because your timeline may contain instances from the
objects that may no longer exist in the Form if the objects were removed or renamed.
The Toolbar at the bottom of the screen contains two popup menus - Insert and Arrange. The far
right button with the trash icon will help you to delete objects.
The Navigation bar in the upper part of the screen contains the button (Code) that switches the
application into Code Mode. In the upper right corner there is an Undo button which helps you
undo operations made on objects.
Design Mode
In Design mode you can insert/remove objects and modify their properties.
Use the Undo button to reverse changes made to objects on the screen.
79
Design Mode
Insert a new Object
To add new objects to the Form tap the Insert button on the baseline toolbar. In the popup
menu, (refer to the list of objects on page 67,) tap your selected object. The new object will be
created on a vacant space in the screen or in the middle of the screen if there is no free space.
The selection menu will collapse after each selection except for a Popup Tag selection. To
collapse the popup without selecting an object, just tap the Insert button.
Move an Object
Objects can be moved to a new space using a slide gesture (see Gestures chapter).
Resize an Object
Objects can be resized by using a resize gesture (see Gestures chapter) or by modifying the
Geometry properties in Inspector. The Geometry property “Locked”, on the Geometry Inspector
bar, must be switched off to be able to resize or move an object.
Modify the properties of an Object
All an object’s properties can be modified by using the Inspector functions. To call
the Inspector , double tap the object. See the Inspector chapter for more details.
To open the Inspector for the Form’s properties, double tap an empty space on the
Form.
You can Undo all changes made to properties in the Inspector screen.
80
Links
Arrange Objects
Every object on the screen has its own Z-position, ie. an order of objects along the Z-axis, which
is perpendicular to the screen. Consider each object as a single sheet in a stack.
When the Form is being constructed, by default, the objects are arranged in order from the top
of the Form with each new object being added beneath the last one on the Form, but ahead or
in front of the former object in the Z-axis.
It may be useful, (in the interests of saving screen real estate), to arrange objects in a stack. Use
the Arrange popup menu, which opens when the Arrange button is tapped.
Bring to Front. takes any object from the stack and puts it at the forefront position.
Bring Forward swaps the object with the closest object forward of it, if any.
Send to Back puts the object to the furthest position rearward.
Send Backward swaps the object with the closest object rearward of it, if any.
Please note that Z-ordering for Popup tags behaves opposite to that of Event Buttons.
Popup tags always follow their target Event when the Event’s Z-order is changed.
Remove an Object
Select an object and tap the trash icon in the lower-right corner of the screen.
Links
A Link is used to automatically activate or deactivate buttons in a CODA Form as a consequence
of how the activity is unfolding. A link may also pass Tag information from a source Tag to a
target Event when the link activates or deactivates the target Event.
The benefit of using Links is to reduce the number of manual button activations and/or
deactivations, (clicks) that an operator would need to perform. The use of links in the Form will
make the coding of your activity more efficient.
Links can be initiated when an Event, Tag or Popup Tag button is activated (button clicked down)
or when an Event button is deactivated (button clicked up).
Link Protocols
A Link may be used to “activate” or “deactivate” a button.
A Link will not be activated unless the Source button is active.
A Link to a Tag button may tag or pass its tag as well as activate the button.
A link will only work in the direction of the link.
A link may be established
– from an Event button to another Event button or to a Tag button
– from a Tag button to an Event button or to another Tag button
81
Links
– from a Popup Tag button to an Event button or to a Tag button
A Link cannot be established :
– from an Event button to a Popup Tag button
– from a Tag button to a Popup Tag button
– from a Popup Tag button to a Popup Tag button
Terminology
An “On activation” link will perform when the source button (Event, Popup Tag or Tag) is
activated. An “On activation “ link originates from the source button icon
which is located on the left side of the button. An “On activation” link is
depicted on the Coding Form as a green link line.
An “On deactivation” link will perform when the source button (Event only) is deactivated. An
“On deactivation “ link originates from the source button icon which
is located on the right side of the button. An “On deactivation” link is
depicted on the Coding Form as a blue link line.
Note : It is important that the user understands that the terminology is in reference to the source
button not to what the link will do to the target button.
Create a link between Objects
To add a link from one object to another, select the object (the source of the link action) by
tapping it. Without lifting your finger, tap the relevant link symbol and drag the link arrow to the
object (the target of the link action) to be linked to and select the action(s) you want the link to
perform to the target button.
Delete a link between Objects
To delete a link, highlight the button (either source or target) to display the links. Double tap on
the object to open the Inspector window. In the Inspector window, scroll down to the “Actions”
or “Inbound Action Links” box. Tap on the relevant box to open the the link function(s) display
and highlight the link function to be deleted. Slide your finger to the right to display the Delete
button and tap the button. Tap the Done button at the top left of the screen to confirm and save.
82
Inspector
Inspector
The Inspector window display depends on the object type and it allows you to modify the
corresponding properties of that object.
The Inspector Screen for the iPhone is a single display which
contains all the Inspector functions. Scroll up or down by swiping
the screen.
Double tap an object on the form and the Inspector screen for that
object type will open.
For the iPad, the edge of
the Inspector screen will
contain an arrowhead
pointer which will indicate
the object that the screen
relates to.
For the iPad, the Inspector
screen will “auto-hide”
when you tap any blank
area on the form.
To Save & Close the Inspector, tap the “Done” button in
the top left of the Inspector or tap the Object.
Object Name
The Object Name bar contains a text field to name the
object. The text in this bar is written into the timeline
during a coding session. This bar is displayed for
Events, Tags and Popup tags.
83
Inspector
Caption
The Caption bar allows you to manipulate the visible
representation of the object’s code name on the
screen. You can switch it on/off and shift it horizontally
and/or vertically from the object’s center.
Even if the caption’s visibility is switched off, it will not
affect the coding process, coding objects will mark
coded instances with their Code Name.
This bar is displayed for Events, Tags and Popup tags.
Shape
The Shape bar allows you to specify the shape of the
object. It can be a rectangle, a rounded rectangle, an
oval shape or turned into a more sophisticated shape
of the image, assigned in the Fill function in the Inspector bar. This bar is displayed for Events,
Tags, Popup tags and Dummies.
Fill
The Fill bar manages the internal style of the
appearance of an object.
None - the object will have no fill.
Color - select any color to fill the object’s shape.
Image - fill the object’s shape with an image.
Gradient - fill the objects shape with a vertical or
horizontal color gradient
Alternatively the image’s shape (different shapes made by using transparent zones in the image)
can become the shape of the object. See Shape’s bar description. This bar is displayed for Events,
Tags, Popup tags and Shapes.
Bevel
This is an ON / OFF slider to give the object a
3-dimensional effect.
Stroke
The Stroke bar manages visibility, color and thickness
of the object’s outline.
This bar is displayed for Events, Tags, Popup tags and
Shapes.
84
Inspector
Text & Attributes
The Text & Attributes bar allows you to modify text
attributes of the selected object, such as color and
alignment. This tab is displayed for linked text boxes
only.
Geometry
The Geometry bar manages the coordinates and the
size of the object’s frame. It also allows you to lock the
frame, preventing it from further changes. This tab is
displayed for Events, Tags, Popup tags, Shapes and Text
boxes.
Actions
Tap the text box to open the Actions display. This
window will display all the actions (including
Outbound Links) that will occur on the activation and
deactivation of this button.
Inbound Action Links
Tap the text box to open the Inbound Action Links display.
85
Inspector
Tag Group
The tag group property sets the parent group for the tag. A tag button can only belong to one
group, but a group can contain as many tags as required. Using tag groups is recommended as
it helps organize and sort tags when using the Matrix, Sorter and Find windows in SportsCode.
When using the tag groups, try to avoid using tags that belong to the same group when coding
a single event. This can create sorting problems in the Sorter window of SportsCode.
Tag Mode
A tag button, when activated, will insert into all active event buttons
except when the tag has an “On-activation” link. In this case, the tag will be
passed down the link, making it possible to exclusively insert the tag into
only one linked event.
Form Properties
The Inspector Form Properties manages the properties
of the Primary Form and also that of any Containers.
The window opens when the empty space on the
Form or Container has been double tapped.
The Fill panel manages the background color of the
Form and Containers.
The Password Protection panel allows you to protect
your Code Form either to open it or to prevent any edit
function. This is available for the Primary Form only.
The Inbound Action Links will be active for a Container
only.
86
Code Mode
Code Mode
Use this mode for coding ie. to create a timeline. Only the single tap gesture is used in Code
Mode.
iCODA supports multi-task and fast app-switch on iOS4.1
During a coding session, if you choose to answer a telephone call or respond to other
notifications, your coding session will automatically be suspended.
iCODA will save your coding and will return you to the Coding Form and current coding session
as soon as you terminate your call. You will be returned to the coding session in real time. ie. the
timeline will be advanced by the duration of the call.
If you do not wish to be interupted during your coding session, we recommended you to switch
your iPhone into the Airplane Mode before starting your coding session.
Switch your iPhone into Airplane Mode before coding.
To activate Airplane Mode tap the Settings icon on your iPhone screen. In the popup Settings
view, Airplane Mode is located on the first position. Slide the switch to ON. In this mode your
iPhone cannot receive any incoming calls or text messages.
Start a Coding Session
The Navigation bar in the upper part of the screen allows you to go back to the Form list or
switch to the Design mode.
Before you start a coding session all the coding objects on the form are displayed “opaque”.
A
B
Code mode awaiting start of coding session (A) and the coding session in progress (B).
87
Code Mode
To start a new coding session with the opened Form tap the Start button on the baseline and a
timeline will be activated. To code, simply tap the relevant button(s).
A coding session timer will appear at the right hand side on the baseline toolbar (see Figure B)
and begin recording the elapsed time.
In the centre of the Baseline is a lock / unlock button.
Click this button to lock the position of the code buttons on the Coding Form. This is to prevent
the Coding Form from being moved inadvertently during coding when the size of the Form
exceeds the size of the screen.
During the coding session you may return to the Design Mode by tapping the Design button in
the navigation bar at the top of the screen. Important: Refer to the Design Mode section of this
manual before adding, amending or deleting objects from your Form during a coding session.
Coding History
When you begin coding in Code Mode, a “History” button will appear in the footer bar at the
base of the screen. As you are coding, the following coding history will be recorded, saved and
available for display and edit.
EDIT Buttons
- Start and End time of each instance
- Tag Buttons attached to each Event
To display the Coding History, just tap the History button and a History
screen will open with the coding history information relative to the
coding file open. This coding history is available to be edited.
The Coding History will be displayed in the chronological order of the
Event start times with the most recent Event displayed at the top of the
window.
If a
graphic is displayed alongside and to the left of the Event
name, this indicates that the Event is still open.
There is a blue arrow graphic
displayed alongside and to
the right of the Event name. Tapping this arrow graphic will
rotate a screen which displays the Start and End times of the
Event.
88
Code Mode
This display has a “pin-wheel” which can be scrolled to edit the Event start and end times in the
Timeline.
An Event may be deleted from the History by swiping the Event name from right to left and then
tapping the Delete button.
NOTE : Caution - This delete function is not reversible
Tags attached to an Event may be added and/or deleted.
To Add a Tag, tap the “Add a Tag” bar and select the Tag you wish to add from the list displayed.
To delete a Tag, swipe the name of the Tag from right to left and tap the delete button.
Saving your Coding
iCODA has an auto-save feature which will save your .coda file and also the related .xml file.
These are updated and saved every 5 seconds.
The file will be saved as the Form Name which you have open for the coding session. If a file
already exists with the form name, then the file will be saved and named with the form name
followed sequentially by (1) , (2) etc.
You are able to change the name of the saved file by specifying another name when prompted
when you stop your coding session.
89
Code Mode
Stop the coding session
When your coding has been done (completed), you stop
the current coding session by tapping the Stop button on
the toolbar. You will be asked to confirm your intention in
the dialog sheet which appears by tapping the Stop Coding
button.
If you have tapped the Stop button by mistake, you may return to your coding screen by tapping
the Coding Form. The coding session timer will still be active until you have confirmed your
intention to stop coding.
After confirming the end of the coding session you will be asked to specify an Output File Name
to save the created timeline. Saved timelines are stored in the memory.
A
B
At the left hand side of the navigation bar on the screen in which you specify a file name, is a
”Cancel” button. This will take you to the screen illustrated in (B) above. If you select “Remove”,
the timeline file will be deleted immediately. This action is irretrievable.
The “Save timeline” button will return you to the screen illustrated in (A) above.
Once a coding session has been stopped, been given a file name and saved; the file will remain
on the iCODA device until the Command Centre in CODA downloads it. You are not able to view
a list of saved files which are stored in iCODA. To remove files from iCODA you must use the
Command Centre.
90
Online Coding
Online Coding
Online Coding is a feature that allows any number of CODA and/or iCODA applications to
participate in a synchronized coding session simultaneously and live via the internet. The CODA
XML data file which is created from the multiple coding inputs is available to be pulled into
SportsCode or Studiocode in real time.
With Online Coding you will “share” a common Timeline in a Coding Session that is hosted on a
CODA Server so that multiple coders can input coding of an Event simultaneously. You will be
using the Coding Form through which you accessed the Network facility, so be very sure that
you have selected the correct form relevant for the Coding Session
For the iPhone, iPod and iPad, there must be either a WiFi connection to a local area network or a
3G internet connection for remote connection to the server.
At the bottom right of the iCODA Coding screen is a button titled “Online Coding”.
When you tap this button, by default, you will be taken directly to the first server available to you
in your LAN. If this is the first time you have logged into a CODA server or if the server you
connected to last time is unavailable you will be taken to the Servers List screen
An upper panel will display the server(s) active in your
LAN only. A lower panel will display the server(s) you have
recently connected to which are not in your LAN.
To connect to another network or computer, tap the “Other . .
. . .” name in the panel. The “Other Server” screen will be
presented.
You must enter the public IP address (or you may choose to
enter the server URL or DNS name ) and port number of the
computer/server you wish to connect to.
Once you have connected to a server, CODA will retain the
server name & address and it will be displayed in the “Recent
Servers” panel of the Servers List next time you enter this
routine.
Tap the “Done” button to connect to the nominated server.
91
Online Coding
If, by default, you have been taken to the first available server in your Server List, (which will
automatically list all the sessions available at that time on that server), but this is not the server
you wish to connect to, tap the “Servers” button at the top left of the screen and you will be
returned to the Servers List.
Tap the server you wish to connect to. This will take
you to the Session List screen which will list the
sessions (if any) which are created and are available to participate in. If there are no sessions
active / available you may choose to create a new session.
Note: When you select “Online Coding”, iCODA will automatically search its memory for servers
which it has previously connected to. Each of these servers which are available will be displayed
for you to choose from. If only one server is available, iCODA will bypass the Server List screen
and take you immediately to the Session List screen to display the sessions (if any) which are
created and available for connection to.
The Coding Session
The coding session may be joined by any number of participants. Access to a session may be
restricted to participants by password. A participant may join and/or leave a session at any time
between when a session is created and when it is stopped.
When a participant joins a session after a coding
session has been started, the participants coding
timer will display the time elapsed from the start
of the coding session (not from the time the
participant joined the session).
The session will be stopped on the CODA Server
only when the last participant disconnects.
The Session Owner
The person / device which creates a session is the
“Owner” of the session. The key function which
the owner must perform is to “Start” a coding
session. No other participant is able to start a
session.
92
Online Coding
Create a New Session
From the ‘Session List” tap the “New Session”
option. The device which creates a new session
will become the owner of the session and will be
required to start the session.
It is mandatory when creating a session to provide
a session name. You may also choose to establish
a password, without which other participants may
not join the session.
Tap “Done” to create the session. If the session is
successfully created, you will be taken directly to
your Coding Form in the Code Mode screen where
CODA will wait for you to Start the session.
Connect to (Join) or Reconnect to a Session
From the Session List Screen, tap the session you
wish to join. If a password is required, input the
password and tap “ Join”. If the password is correct,
you will join the session and you will be taken
directly to your Coding Form in Code Mode.
93
Online Coding
If the session has not been “Started”, the Code Mode
screen will be “greyed out” which will prevent you
from activating any code button(s), but you will
still be connected to the session. A spinning wheel
symbol will indicate that you are connected and
that you are waiting for the session to start.
There is an Online Coding status indicator located on the Coding Session Timer which indicates
that you are connected to the server if it is green. When the connection is broken it turns red.
Start a Session
If you are the device which has created a session, you will be required to “Start” the session. No
coding of the session can take place by any device connected to the session until the session is
started. The creator of a session will have the “Start” button at the bottom left of the “Session
Name” screen. When this button is tapped, the Code screen will become clear and you may
begin coding. The Code screens on all other devices connected to the session on the server will
change from “greyed out” to clear to indicate that the session has been started, and the session
timer will be activated.
94
Online Coding
Start Coding
Once the session owner has started the session, the Code Mode screen will become clear and
you may begin coding. If the session is in progress when you join, the Code Mode screen will be
clear and immediately available for coding.
Session Timer and Synchronization
Once a session has been started, all the session participants, (including the Session Owner,)
become equal participants as far as the CODA server is concerned. At the bottom right of a
participants coding screen a timer displays the server time elapsed since the session was started.
All participants will display the time elapsed since the start of the session irrespective of when
they joined the session. This ensures that the coding from all participants is synchronized with a
common timeline.
Note: It is conceivable that an event could be coded live from devices located in varying time
zones. In such an instance, CODA uses UTC as a reference time. (UTC is Coordinated Universal
Time which replaced Grenwich Mean Time {GMT} as the world standard time. For CODA
purposes, UTC and GMT may be considered as being the same.) For synchronization purposes,
the CODA server is concerned only with time synchronization between itself and all the session
participants. If there is to be any third party application pulling the timeline data from the CODA
server they must ensure that these computers are also synchronized with their network time.
95
Online Coding
Disconnect from / Stop a Session
You may deliberately disconnect from the session at any time by tapping the “Disconnect”
button at the bottom right of the Code Mode screen. If the Online Coding status indicator which
is located on the Coding Session Timer changes from green to red during an online coding
session, this indicates that the connection to the server has been broken. CODA will
automatically attempt to re-establish the connection. A disconnection which is not deliberate
will not affect your coding records because CODA saves your coding data at your device and
sends it to the server at intervals. Coda records what data has been transmitted to and saved by
the server and as soon as the reconnection is established, CODA will “catch up” on the data
coded during the period of disconnection.
You may stop your coding session at any time by tapping the “Stop” button. You will be asked to
confirm your intention in the dialog sheet which appears by tapping the Stop Coding button.
If you have tapped the Stop button by mistake, you may return to your coding screen by tapping
the Coding Form. The coding session timer will still be active until you have confirmed your
intention to stop coding.
Data Transfer and Storage
CODA stores the data coded by each device on that device and it also transmits the stored
data at intervals to the CODA Server. If the connection between the device and the server is
broken, the device will continue to save the coding data. It is recommended that you retain the
complete timeline file after you have deliberately disconnected from the server until you have
confirmed that your entire timeline file has been received by the server.
96
Email a Coding Form
Email a Coding Form
You must have an active email account setup as a pre-requisite of this function. If you have more
than 1 email account, the default email account will be used.
To email a Coding Form, in the Forms List tap the Coding Form to select it, then tap the Email
button. In the email screen, tap the address line ( To: ) to activate the addressee edit screen.
Enter the addressee details either by tapping the
symbol to activate your Address
Book, or by typing the details from the keyboard
, ..........then tap the Send button
When your iCODA designed form is imported by Sportstec Gamebreaker (STGB), all the Event
buttons, Shapes and Text boxes will be visible and they will retain all the properties and
appearance characteristics which had been ascribed to them. But, Popup Tag and Tag buttons
and any links which exist in your Coding Form, will not be present.
97
Email a Timeline
Email a Timeline
You must have an active email account setup as a pre-requisite of this function. If you have more
than 1 email account, the default email account will be used.
To email a Timeline, tap the Timeline Name to select it, then tap the Email button. In the email
screen, tap the address line ( To: ) to activate the addressee edit screen. Enter the addressee
details either by tapping the
symbol to activate your Address Book, or by typing the details
from the keyboard ,
..........then tap the Send button.
You will be returned to the Timelines list. The
Timeline which has been emailed will display
an envelope within the Timeline icon adjacent
to the Timeline Name.
When your Timeline is imported by Sportstec Gamebreaker (STGB), Popup Tag and Tag
information will not be available in the STGB Timeline.
98
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement