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

Apply better screen nomenclature to video system #1387

Open
MooglyGuy opened this issue Sep 10, 2016 · 1 comment
Open

Apply better screen nomenclature to video system #1387

MooglyGuy opened this issue Sep 10, 2016 · 1 comment

Comments

@MooglyGuy
Copy link
Contributor

Currently the code uses a bunch of different terms, sometimes interchangeably, for what ends up being four different conceptual things:

Screen: The video output from a driver. A driver can output 0..N screens.
Display: The physical device displaying 1..N screens. In real life, this can be a raster CRT, many different kinds of LCD, a vector CRT, or even multiple superimposed video outputs on one raster CRT.
Window: The display area on the host machine. A host machine can have 1..N windows.
View: The manner in which 0..N displays are shown on a given window.

For example, in a Cocktail View of a 1-Screen game, there will be 2 Displays shown in 1 Window, with each Display showing the output of that single Screen, but with different transforms.

These associations are simple and easy to remember, but due to different people working on different parts of the overall "video signal chain" code in MAME, over wildly different time periods, much of the code has not been structured with this in mind. So, someone (probably me) needs to go through and make the code more robust, and rename things for clarity as needed.

@ghost
Copy link

ghost commented May 10, 2017

Also noting here (way late, but still important) that documentation will need to follow the nomenclature of the code when that gets settled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants