summaryrefslogtreecommitdiffstatshomepage
path: root/src/mame/drivers/mpu12wbk.c
diff options
context:
space:
mode:
author Aaron Giles <aaron@aarongiles.com>2013-07-26 08:15:05 +0000
committer Aaron Giles <aaron@aarongiles.com>2013-07-26 08:15:05 +0000
commitec07fb10225293829c870f2ce1ffd05732f671ca (patch)
tree5fed58d5c5d4ecf690475e91f3546036a14abdd8 /src/mame/drivers/mpu12wbk.c
parentb5e744c477c41c28d1cefb88c622ae3a1cd4eb4e (diff)
Fix long-standing architectural wart: the priority bitmap is no longer owned
by the tilemap system, and no longer exists globally in the machine. Instead it is allocated per-screen for all systems. This has several side-effects: 1. Previously, the pdrawgfx* functions were already changed to take the priority bitmap as a parameter. Now all other hand-crafted functions that mess with the priority bitmap generally must do so as well, and have been updated. 2. Calls to the tilemap system now need to provide a screen_device. This is not just for the priority_bitmap, but also for screen flipping, which previously always assumed the "primary screen" when doing flipping calculations. 3. All devices that implemented tilemap-like functionality have been updated to follow the same pattern, since they largely tend to call through to the core tilemap system at some point.
Diffstat (limited to 'src/mame/drivers/mpu12wbk.c')
-rw-r--r--src/mame/drivers/mpu12wbk.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mame/drivers/mpu12wbk.c b/src/mame/drivers/mpu12wbk.c
index 738a06e69a2..562419a5279 100644
--- a/src/mame/drivers/mpu12wbk.c
+++ b/src/mame/drivers/mpu12wbk.c
@@ -279,7 +279,7 @@ void mpu12wbk_state::video_start()
UINT32 mpu12wbk_state::screen_update_mpu12wbk(screen_device &screen, bitmap_ind16 &bitmap, const rectangle &cliprect)
{
- m_bg_tilemap->draw(bitmap, cliprect, 0, 0);
+ m_bg_tilemap->draw(screen, bitmap, cliprect, 0, 0);
return 0;
}