`Template for control panels (default for non-openended instruments, may be slightly wrong in the details):`

Current session: test3 | Main |
scenario Load a scenario Create a scenario | participants Show participants Update Are participants being accepted? Accept new participants Only accept rejoins Do not accept new participants | download/save
? takeSnapshot ? post a CAP file: session or round ? Save, or append, control-panel database to file or server archive File Server General File Server User File Server Results File Server Participants ? Download server archive to a window, or to workData control-panel database Window | workData | General Users Results Participants History CUSTOM Submitted data You can also view submitted data with Data -- Submitted |
| vuHistory Toggle display of the history of prior actions Toggle display of the intermediate actions | Data | UserStatus | toWindow | ReadFile | Notes Message:
--- | --- | --- | --- | --- | --- | --- | --- | ---

Results
Clear
Form
Clear
Top
| 00:00

Task history: |  |

09:24:02 pm ...

Suggestions... Next task ... Control panel...
Click here to re-display tasks table
a suggestion

#### Prior suggestions (newest at the bottom)

Pre-Session tasks | Allow new participants to join session Load a scenario file (optional) ? Note: if you first load a scenario file, its values will be used when you `Create CAP files` Assign reference data, take a snapshot, and create CAP files (do this after, optionally, loading a scenario file) Start the session (step 1) ? (display generic hello page) (do both steps) Start the session (step 2) ? (display first page of the instrument) custom pre-session tasks can be displayed here | ? Default status (participants can not join) New participants can join, and current participants can rejoin. New Participants can not join, current participants can rejoin New Participants can not join, current participants can not rejoin A scenario file was loaded. CAP file has NOT yet been created. CAP files have been created. Session not yet started Session has started (step 1: participants will see the generic hello screen) Session has really started (step 2 completed: participants will see the first page of the instrument)

Generic tasks | click to toggle display of several generic tasks...
Update client accessible parameter files? (3 choices) | Load a scenario file, and then use its values to update the ROUND and SESSION client-accessible-parameters file Update client-accessible-parameter (CAP) files: SESSION, Round, or Both (using current control panel data) Read a snapshot file, change control panel data, and update client accessible parameters files |
Retrieve submitted data, or a results file? (2 choices) | Get, from the server, this round's submitted data, and the list of participants Get an XML file containing results (as produced by an external program) |

generic tasks... Session tasks ... |
custom task table, task link | custom task table, task description
custom task table, task link | custom task table, task description
etc | etc

Contents of forms are displayed here

Date of last task
History of actions displayed here, with oldest at the bottom.
Results from recently completed tasks are written here.

Click the to display the results of the `<alert>`
| `<alert where="ALERT"> alert message: ALERT </alert>`
| `<alert where="STATUS"> alert message: STATUS </alert>`
| `<alert where="TASKBAR"> alert message: TASKBAR </alert>`
| `<alert where="STATUS_FINAL"> alert message: STATUS_FINAL </alert>`
| `<alert where="STATUS_INTER"> alert message: STATUS_INTER </alert>`
| `<alert where="SUGGEST"> alert: SUGGEST message (control var nthSuggest= <show var="nthSuggest" />) Here! ; </alert>`
| `<alert where="DATAMESSAGE"> alert message: DATAMESSAGE </alert>`
| `<alert fade="1" seconds="12" where="DATAMESSAGE"> alert message: DATAMESSAGE, fade in 12 seconds</alert>`

Click the to display the results of the `writeDoStatus(...)`
| `writeDoStatus("(1) writeDoStatus, using ' '",'[Using writeDoStatus header]',' ');`
| `writeDoStatus("(2) writeDoStatus,using reset (date bar is written in history block)','[Using writeDoStatus header]','RESET');`
| `writeDoStatus("(3) writeDoStatus, using NOWRITE",'[Using writeDoStatus header]','NOWRITE')`
| `writeDoStatus("(4) writeDoStatus, using NOSAVE",'[Using writeDoStatus header]','NOSAVE')`
| `writeDoStatus('(5) writeDoStatus, using FINAL",'[Using writeDoStatus header]','FINAL')`
| `writeDoStatus('(6) writeDoStatus, using INTER",'[Using writeDoStatus header]','INTER')`

Click the to display the results of the `writeLastAction(...)`
| `writeLastAction('(a) writeLastAction("message") is displayed here (newest at top)! ')`
| `writeLastAction('(b) writeLastAction("message") is displayed here (newest at top)! ')`
| `writeLastAction('(c) writeLastAction("message") is displayed here (newest at top)! ')`

| <submit do=myAct1" summary="last action: submit do=myact1"> Submit using myAct1 </submit >
| <div doStuff="doSt1" summary="last action: doStuff = doSt1"> doStuff="dost1" </div>
| <div doForm="form1" summary="last action:form1" >doForm: form1 </div >
| <radio do="rad1" value="1" name="optX" summary="radio: rad1=1"> 1 </radio > <radio do="rad1" value="2" name="optX" summary="radio: rad1=2"> 2 </radio >

Click the to display the results of the `<display >`
| <display type="inline">disp2 </display>
| <display type="block">disp1 </display> <display type="none">disp1 </display>
| <display type="block">disp1 disp3 </display> <display type="none">disp1 disp3 </display>
| <display type="block" clear="1" >disp4 </display>
id | the div
--- | ---
`disp1` | This is the id="disp1" div
`disp2` | This is disp2= the disp2 span!
`disp3` | This is the id="disp3" div
`disp4` | This is the id="disp4" div, that will be cleared

Description of session ...

test3 | ss

Details...
xxx