Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kaneko/kan_pand.cpp: Use device_gfx_interface for gfx decoding behavior, use correct type for variables #11793

Merged
merged 2 commits into from Nov 29, 2023

Conversation

cam900
Copy link
Contributor

@cam900 cam900 commented Nov 28, 2023

kaneko/airbustr.cpp: Fix out of range issue

@cam900 cam900 changed the title kaneko/kan_pand.cpp: Use device_gfx_interfacce for gfx decoding behavior, use correct type for variables kaneko/kan_pand.cpp: Use device_gfx_interface for gfx decoding behavior, use correct type for variables Nov 29, 2023
* Use standard write line signature for set_clear_bitmap.
* Don't split member initialisation across files.
Comment on lines 39 to 46
void set_clear_bitmap( int clear );
void set_clear_bitmap( bool clear );
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably stay as int so it uses the standard devcb write line signature in case anything tries to hook it up that way.

@cuavas cuavas merged commit e9ab842 into mamedev:master Nov 29, 2023
5 checks passed
Luigi30 pushed a commit to Luigi30/mame that referenced this pull request Dec 16, 2023
…amedev#11793)

-kaneko/airbustr.cpp: Fixed offset of CALC1 chip in devram.
einstein95 pushed a commit to einstein95/mame that referenced this pull request Mar 2, 2024
…amedev#11793)

-kaneko/airbustr.cpp: Fixed offset of CALC1 chip in devram.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants