summaryrefslogtreecommitdiffstatshomepage
path: root/src/mame/drivers/namcos23.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/namcos23.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/namcos23.c')
-rw-r--r--src/mame/drivers/namcos23.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mame/drivers/namcos23.c b/src/mame/drivers/namcos23.c
index ff5f2bcbcac..c2590e158f1 100644
--- a/src/mame/drivers/namcos23.c
+++ b/src/mame/drivers/namcos23.c
@@ -2162,7 +2162,7 @@ UINT32 namcos23_state::screen_update_s23(screen_device &screen, bitmap_rgb32 &bi
m_bgtilemap->set_palette_offset(m_c404.palbase);
if (m_c404.layer & 4)
- m_bgtilemap->draw(bitmap, cliprect, 0, 0);
+ m_bgtilemap->draw(screen, bitmap, cliprect, 0, 0);
return 0;
}