the finder's owner. This meand you no longer need to care about the
your relationship to the object being configured and a lot of ^ and :
can disappear. There's a bit reduction in string pasting in macros from
this.
Yes, I have to make this apply to devcb etc. as well, but that's a job
for another day.
There's probably at least one thing broken by this where optional
objects are involved. Most things can be solved by just getting rid of
the now-problematic ^ and : prefixes.
- Write callbacks can now be configured as `OUTPUT("item_name")`. This behaves equivalently to a zero-dimensional `output_finder`, while eliminating the need to instantiate and resolve this in driver classes separately from the callback itself.
- The width of a callback's default mask now properly depends on its type (as was half-implemented before), instead of always being reset to 0xffffffffffffffff when actually configured. This allows MCFG_DEVCB_INVERT to work with line write callbacks as one might logically expect.
--------------------------------
Centipede (Japan) [ShouTime, Javier Vidal Mata, Sean Sutton, Candy Wolff, Evan Korzon, Surgeville, Dane Biegert, Charles MacDonald, Smitdogg, The Dumping Union]
* Allow AES joystick to be connected to arcade systems with D-sub connectors (common for "consolised" use)
* Pass through Select input from D-sub connectors on JAMMA variants
* Default to Japan BIOS for fixed software using mahjong panel (Euro BIOS doesn't support mahjong panel)
* Use JAMMA joystick panel for mahretsu since (doesn't support mahjong panel in MVS mode)
* Allow controls to be changed for MVS mahjong games (only BIOS and bakatono support joysticks, but still useful)
----------------------------------------------
Grand Champion (set 2) [Malcor, MASH]
New working clone added
---------------------------------------------
Grand Champion (set 3) [Malcor, MASH]
Concrete device types now have a call operator that instantiates a
device.
This change means you *must* use DECLARE_DEVICE_TYPE to declare the
public interface of your device, even if it's device_t. If you want
to use private implementation classes, use DEFINE_DEVICE_TYPE_PRIVATE
and instantiate the object finders.
