summaryrefslogtreecommitdiffstatshomepage
path: root/src/emu/dipalette.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Eliminate ARRAY_LENGTH template in favor of C++17's std::size AJR2021-02-141-1/+1
| | | | | | | | | | * osdcomm.h: Move definition of EQUIVALENT_ARRAY to coretmpl.h * sharc.cpp, gt64xxx.cpp, ym2413.cpp, gb_lcd.cpp, snes_ppu.cpp: Use STRUCT_MEMBER for save state registration * gio/newport.cpp, megadrive/svp.cpp, nes_ctrl/bcbattle.cpp, arm7.cpp, tms9995.cpp, pckeybrd.cpp, sa1110.cpp, sa1111.cpp, jangou_blitter.cpp, vic4567.cpp: Use std::fill(_n) instead of memset * emucore.h: Remove obsolete typedef
* (nw) misc cleanup: Vas Crabb2019-09-201-1/+2
| | | | | * get rid of most assert_always * get rid of a few MCFG_*_OVERRIDE
* dipalette: Fix faulty assertion that was breaking nes_vt.cpp in debug builds ↵ AJR2018-05-061-1/+1
| | | | (nw)
* Various palette and screen improvements (nw) AJR2017-11-131-5/+1
| | | | | - Use device_resolve_objects to remove the need for resolve_palette - Palette format no longer depends on configuration of first screen
* Disallow a negative number of palette entries by changing some types (nw) AJR2017-04-161-2/+2
|
* dipalette: A return to sanity (nw) AJR2017-04-161-18/+31
| | | | | * Revert entries(), indirect_entries(), shadows_enabled() and hilights_enabled() to return the configuration parameters instead of accessing the live state. The thought behind the implementation change was that palette devices could potentially determine the number of entries from the sizes of devfind objects. The regressions caused by this have been worked around, but it was probably a bad idea in the first place. * Zero-entry palettes are no longer valid. The code that tried to support them was basically left over from when every running machine had a single global palette.
* New device interface for palettes AJR2017-04-061-0/+503
- Create device_palette_interface, which takes over most functionality from palette_device except for the initialization/decoding routines and RAM interface. - Update screen_device and device_gfx_interface to use a device_palette_interface object rather than a palette_device. This necessitates slight alterations to a few drivers and devices. - Modify v9938 and v9958 to use the new device_palette_interface rather than a subdevice. This entails breaking a cyclic dependency between device_video_interface and screen_device for this case.