The Complex Coding Mode, was developed to log multi-level codes for multiple subjects* during live observations.
The main problem during a live observation is, that you can not simply 'pause' the situation or even 'replay' the it, to log additional Events or Codes, that describe the situation in more detail. That is why the Lexical coding mode does not work for live observations in combination with multi-level Codes.
The complex coding mode can be used for video based observations as well, but that is most often unnecessarily hectic.
Activate Coding Mode
▪Click Start - Observation - Observation settings 
.
▪Select the Coding mode Complex.
▪Click OK to confirm your settings.
Characteristics of this Coding Mode
 | Complex - This coding mode allows you to log multi-level Codes per subject, during live observations. For this routine, each subject always has a active Event during the observation. This means that you need a Code for every possible situation/condition, for each first level code, throughout the video! A subordinated NILL code can cover the parts that are not of interest to you. |
Note: The Complex coding mode, does not automatically pause the video!
So in most video based cases, the Lexical (Post-hoc) coding mode is the better choice.
This Complex coding mode was designed to:
oLog multiple Events simultaneously (multi-channel) during a live observation.
oCreate a continuous stream of Events, for each first level Code.
oCreate Events with duration only.
oUse multi-level coding systems during life observations.
oEnter multiple Codes per Event, using lexical chains.
oCreate context based Classes (column headers) -in real time while coding- based on the Code just chosen.
oImplement complex coding systems, with the help of 'Prefixes' .
oCreate combined Codes on the fly, in combination with the option Combine Codes.
•
| TIP: | Anyone choosing either the Lexical (post-hoc) or Complex coding mode, should also take a peek at the possibilities described in Create context based Classes and in the Coding facial expressions example. |
The Idea
You simultaneously start a separate Event for each top-level Code (subject*) and specify its condition or behavior right from the start. Each Event remains open, until the situation changes.
The moment the situation changes for a subject, its corresponding first-level Code is clicked and the new situation specified. This results in ongoing Events for all Subjects.
IMPORTANT: All Events are logged with duration, NO 'frequency only' Codes possible!
*The terms 'subject' and 'behavior' should be considered rather broadminded, because codes could also be used for e.g. counts in different areas and the 'Master' objects do not necessarily need to be people or animals but could be used to describe e.g. accommodations or areas.