A console dashboard map defines which console dashboards are used by a console theme by mapping the dashboards to map keys.
The map is a set of key/value pairs. Each key maps to zero or more console dashboards.
Each segment on a betting schedule references a console dashboard map key.
When a new level becomes active, a two-step process if performed to determine which dashboards to display
The benefit of the console dashboard map is that it prevents betting schedules from being dependent on individual console dashboards. This enables you to more easily take a betting schedule and plug in a new theme over the top of it.
Let's say you use the exact same betting schedule for every tournament, but you're the kind of person who likes to make the tournaments more fun by using different dashboards depending on the theme of your tournament. Without the map, you'd have to go in and modify the betting schedule to point at the right dashboards for every single tournament. With the map, you only need to modify the console theme.
There are four special keys in a console dashboard map:
If a segment does not reference a map key explicitly, then the default key for that type of segment is used.
If the defined map key does not reference any models, then the default core models (defined by Dr. Neau) will be used.
A tournament has a betting schedule. A tournament also references a console theme.
A console theme has a console dashboard map that references console dashboards. The console dashboards are associated with static keys in the console dashboard map. The keys do not change from map to map.
A betting schedule has segments that reference static keys in the console dashboard map.
The console uses the following information to determine which console dashboard to display: