Table Data Manager - syd711/vpin-studio GitHub Wiki
Table Data Manager
The Table Data Manager is the center where all table meta-data sources are gathered. It helps you to configure every table correctly so that the highscores can be extracted (if supported). Open it via double-click, the toolbar button, or Ctrl+O from the table overview.
The dialog is split into tabs: Score Data (see Highscores), Options (see Script Options), Tags & Comments (see below), Playlists, Meta Data (the auto-filled fields below), Settings, Extras, Screens (see below) and Statistics (see Table Statistics).
Score Data Tab
Statistics Tab
Auto-Filled Fields
When the auto-fill action of the Table Data Manager is used, the following fields will be filled:
- Game Year
- Author
- Game Version
- Numer of Players
- URL
- IPDB Number
- Game Theme
- Designed By
- Manufacturer
- Game Type
- Details
- Tags
Auto-fill data is resolved from the table's Virtual Pinball Spreadsheet match. Use Auto-Fill (or Auto-Fill All when multiple tables are selected) to trigger it - a settings dialog lets you choose exactly which of the fields above should be written, plus an Overwrite existing values option that controls whether fields that already have a value get replaced or only blank fields get filled. This selection is remembered for next time.
Auto-Fill Settings
Comments & Tags
The Tags & Comments tab lets you keep personal notes on a table and add filterable tags.
Comments are shown as colored markers in the status column of the table overview. Three special prefixes are recognized and can be inserted with one click: //TODO to mark a note as a task, //ERROR to mark it as an error hint, and //OUTDATED to mark the table as outdated.
Tags are entered into a separate autocomplete field below the comment - start typing to get suggestions from tags already used elsewhere, or create a new one. Tags can also be applied in bulk from the table overview; see Bulk Tagging.
Tags & Comments Tab
Screens
The Screens tab controls which frontend displays stay visible while a table is actually being played, overriding the emulator-wide default for this one table. Normally all frontend screens (Backglass, DMD, Topper, etc.) hide once a table launches into gameplay - checking a screen here keeps its window on top during gameplay instead.
- Use Emulator Defaults - clears any per-table override so the emulator's global setting applies.
- Hide All - forces every screen to hide during gameplay for this table, regardless of the emulator default.
- Individual checkboxes per screen (Topper, DMD, Backglass, Playfield, Music, Full DMD/Apron, Wheelbar, Loading, Other, Flyer, Help - only the screens your frontend actually supports are shown) let you keep specific displays on. The Music checkbox should only be used if the table actually plays files from its music folder.
Screens Tab
Script Options
For VPX tables, the Options tab exposes any options the table's script declares via VPX 10.8's Option()
scripting feature - the same options you'd normally only be able to change by editing the script. Numeric options are
shown as sliders (with the script-declared min/max/step), and options with named choices are shown as dropdowns.
Values are not written back into the .vpx script - they're saved into the table's .ini file (the same file
described in Table INI File), under a
[TableOption] section, which VPX reads at table load to override the script's declared defaults.
If a table's script doesn't use Option() calls, this tab will simply show no options to configure. Use Reset to
Defaults to clear all per-table overrides and fall back to the script's own defaults.
Script Options Tab