Warning
This documentation is for an unreleased version of MPF!
This is the developer documentation for MPF 0.54, which is the “dev” (next) release of MPF that is a work-in-progress. Use the “Read the Docs” link in the lower left corner to view the developer docs for the version of MPF you’re using.
self.machine.playfield_transfers.*¶
-
class
mpf.devices.playfield_transfer.
PlayfieldTransfer
(machine, name)¶ Bases:
mpf.core.system_wide_device.SystemWideDevice
Device which move a ball from one playfield to another.
Accessing playfield_transfers in code
The device collection which contains the playfield_transfers in your machine is available via
self.machine.playfield_transfers
. For example, to access one called “foo”, you would useself.machine.playfield_transfers.foo
. You can also access playfield_transfers in dictionary form, e.g.self.machine.playfield_transfers['foo']
.You can also get devices by tag or hardware number. See the DeviceCollection documentation for details.
Methods & Attributes
Playfield_transfers have the following methods & attributes available. Note that methods & attributes inherited from base classes are not included here.
-
event_transfer
(**kwargs)¶ Event handler for transfer event.
-
format_log_line
(msg, context, error_no) → str¶ Return a formatted log line with log link and context.
-
raise_config_error
(msg, error_no, *, context=None) → NoReturn¶ Raise a ConfigFileError exception.
-
transfer
()¶ Transfer a ball to the target playfield.
-