Skip to content
ChronoFEED TABLEAU Help

View types

A view's “Chart” (View tab of the editor) says how its elements repeat: a free-form card per athlete, a table row per athlete, a card per race, a row per race in the schedule, or a card per athlete in EVENT's overall standings.

The geometry of a view

┌─────────────────────────── screen 1920 × 1080 ───────────────────────────┐
│  BANNER: X and Y counted from the corner of the SCREEN                   │
│  (competition, time, clocks, message, logo…)                             │
├── Banner height + 6 ─────────────────────────────────────────────────────┤
│ ┌───────── card 1 ─────────┐┌───────── card 2 ─────────┐ ← “Columns”     │
│ │ CARD elements: X and Y   ││                          │   cards per row,│
│ │ from the corner of the   ││                          │   each “Column  │
│ │ CARD                     ││                          │   width” wide   │
│ └──────────────────────────┘└──────────────────────────┘                 │
│ ┌───────── card 3 ─────────┐┌───────── card 4 ─────────┐ ↕ “Row height”  │
│ …                                                                        │
├── Bottom margin ─────────────────────────────────────────────────────────┤
└──────────────────────────────────────────────────────────────────────────┘

An element's “In the banner” box says in which frame of reference its position is read: the screen or the card. A card element is drawn once per card; a banner element, only once (for an athlete: the leader of the reference race). Cards that do not fit are shown in pages.

Athlete cards (repeated area)

One card per athlete, its elements placed freely in the card; “Columns” cards per row. The most common type: the delivered view “Classement (par défaut)” (one row per athlete), the model view “Exemple-Presentation” (two cards per row, a round photo) or an overlay at the bottom of the picture.

The model view “Exemple-Presentation”: two cards per row, for introducing the athletes of a loaded race.

The cards come from the view's races, race after race (in the FINISH race order), each with its athletes kept by the filters and sorted. In a team pursuit, every athlete of every team has a card.

Athlete table (one row per athlete)

1234
An Athlete table view during final A of the 1000 m Women at the Omnium Hollywood short track (111 m).
  1. The header row: the title of each column, with its own style.
  2. One column per card element, arranged from left to right according to their Offset X.
  3. The lap columns: “N” (the last lap completed), “N-1”, “N-2”…, as many as “Columns (laps)”, in the style of the “Lap formatting” element.
  4. The banner: the race, the race clock and “Timer info” (“Last lap”).

The elements become cells placed end to end, each with its own width (at least 40 pixels) and the row height; their position only sets the order. The cell text follows each element's Text section; the header, the Column header section; the header height, the View tab (the number of lines per page takes it into account). See the scenario An athlete table.

Race cards

12345
A Race cards view during the 1000 m Women: the two pairs of group G1 on the track, the next pair loaded.
  1. The race name and its information (“Racing”, “Pending”).
  2. “Race timer”: the running clock; at the end, the highest final time.
  3. “Lap counter”: the laps that will remain after the next crossing of the line.
  4. The race leader (the athlete in position 1): their starting colour, their name, their last lap.
  5. A loaded race: no clock or leader yet.

One card per race in the view. The card also carries the leader: the athlete fields show the first athlete in the race. The fields “No. of laps to go” and “No. of laps completed” are those of the race. The athlete filters (start positions…) do not apply to race cards. See the scenario A race card view.

Schedule

One card per race in the session schedule broadcast by FINISH (sent again every second). By default, only the races in progress (loaded, in progress, finished according to the allowed states); with Schedule: also races not run yet and races already run, the whole session — the upcoming races and those already run —, but never an athlete, a lap or a time: only the name, the competition, the distance and the pair.

EVENT overall standings (one card per athlete, page by page)

123456
The delivered view “Classement général (par défaut)”: page 2 of the 500 m Women of the Coupe Hollywood, broadcast by EVENT.
  1. “EVENT standings, event”: the name broadcast by EVENT.
  2. “EVENT standings, race”.
  3. “EVENT standings, official or provisional”: all the races of the event made official, or not yet.
  4. “EVENT standings, page x / y” (empty when the race fits on one page).
  5. The rank, “16=” for a tie; the round avatar, the name, the club, the country, the time and the gap to the first.
  6. The code (DNF, DQ…); an unranked line has no rank.

Nothing from FINISH goes into its cards: one card per line of the standings on the current page. The banner keeps the information that does not depend on any race (time, date, message, logo). The second display algorithm:

  1. the races in the rotation: those EVENT broadcasts, kept by “Races shown”, in the view's “Race order”;
  2. the split: “Lines per page”, or as many as fit in the card area;
  3. a page is never cut: its lines are frozen when it starts; a correction received meanwhile appears on the next page;
  4. every “Page (s)” seconds, the next page; after the last page of a race, the next race; after the last one, the first;
  5. a race withdrawn by EVENT while it is shown immediately gives way to the next one.

Its fields are the “EVENT standings” fields. With no choice in the panel, or if the chosen view is not of this type, the “Overall standings” moment shows the delivered view. A view of this type has no header row. See the scenario EVENT's overall standings.

EVENT event programme (sessions, blocks and breaks)

12345
The bundled “Event programme (default)” view at 9:15: the resurfacing is in progress, the second 1500 m Women block is next.
  1. “EVENT programme, event name”.
  2. “EVENT programme, current block” (in amber).
  3. “EVENT programme, next block” and “EVENT programme, time of the next block”.
  4. One card per session, block and break: start – end, type, name, duration, state, number of races.
  5. The current card (amber) and the next one (blue): their elements that have a background take the view's colour.

The schedule that EVENT sends (Schedule tab, “Send to TABLEAU”): one card per session, block and break, in program order, with the name, start, end, duration and number of races; nothing about athletes or times. Depending on the time, the card of the current block (or break) and that of the next one are highlighted: their elements that have a background take the view's “Current block” (amber) or “Next block” (blue) colour, with black or white text depending on the background. “Only what is not finished” removes what is over. Cards that do not fit go page by page.

The programme comes through the link to EVENT (“Receive the EVENT overall standings” box of the panel), with the same display delay; nothing is shown after 15 s of silence from EVENT. The bundled “Event programme (default)” view and the “Exemple-ProgrammeEvenement” template are chosen for a scenario moment (the break, the presentation…). Its fields are the “EVENT programme” fields; the header ones (current block, next block and its time, event) also work in any other view. The editor preview shows a sample programme around the current time.