Warning

This is the documentation the latest work-in-progress version of MPF!

This is the documentation for MPF 0.56, which is the “dev” (next) release of MPF that is a work-in-progress. This is probably ok, and means you’ll be on the latest, cutting-edge version of MPF.

However, if you want a more stable version, select the v:stable version from the lower-left corner of this page, which is the most recent version that is not getting new updates.

If you are new to MPF, we have recently rewritten the installation process which only applies to this “latest” 0.56, so you probably want to stay here because the prior installation process doesn’t work on the latest OS and Python versions.

Widget player

The widget player is a config player that’s used to add or remove widgets to existing slides on a display. (This player is part of the MPF media controller and only available if you’re using MPF-MC for your media controller.)

Note that the widget player is a config_player, so everything mentioned below is valid in the widget_player: section of a config file and in the widgets: section of a show step.

Full instructions on how to use the slide_player are included in the Widgets section of the documentation. The stuff here in the config reference is for reference later. You can test slides and widgets interactively using Interactive MC (iMC).

Generically-speaking, there are two formats you can use for widget_player entries: “express” and “full” configs. Express configs will look like this:

widget_player:
  event1: widget1
  event2: widget2
  event3: widget3

This example is tested to be valid MPF and MPF-MC config. However, it is not integration tested. Some parts are hidden. Click to show full config.

widgets:
  widget1: []
  widget2: []
  widget3: []
widget_player:
  event1: widget1
  event2: widget2
  event3: widget3

Full configs will look like this:

widget_player:
   event1:
      widget1:
         <settings>
   event2:
      widget2:
         <settings>
   event3:
      widget3:
         <settings>

In both cases, these configurations are saying, “When event1 is posted, add widget widget1. When event2 is posted, add widget2. Etc.”

This “express” config is down-and-dirty, with no options, to just add widgets to the current slide on the default display. The full config lets you specify additional options (based on the settings detailed below).

For example, the following config will add widget_1 when some_event is posted, but it will also override the default settings and add widget to the slide called slide_2, even if that’s not the current slide that’s showing.

widget_player:
  some_event:
    widget_1:
      slide: slide_2

This example is tested to be valid MPF and MPF-MC config. However, it is not integration tested. Some parts are hidden. Click to show full config.

widgets:
  widget_1: []
widget_player:
  some_event:
    widget_1:
      slide: slide_2

Usage in config files

In config files, the widget player is used via the widget_player: section.

Usage in shows

In shows, the widget player is used via the widgets: section of a step.

Config Options

See widget_player: for config details.