-
Notifications
You must be signed in to change notification settings - Fork 4
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
Screen handling #83
Comments
Also, the BLANK signal should disable RGB output. But according to schematics, the GLUE BLANK signal should not affect the monochrome output signal. On the other hand, @troed claims there is some blanking going on. As well it must, or else the retrace should be visible on the monitor. More research needed. Possibly, the shifter blanks the signal itself? |
Added BLANK in #86. |
BLANK could be used to calibrate the width of the screen window, and the Vsync signal could be used for th window height. |
It may or may not be a good idea to allow two connected screens: one colour and one monochrome. That would open two windows. The |
RGB and monochrome output goes to different pins. So screen_draw needs to be split in two: _rgb, and _mono. Only one should be active at one time. Which one depends on the monitor_sm124 flag.
Why does this matter? E.g. temporarily switching from colour to mono should result in some black pixels on the screen.
The text was updated successfully, but these errors were encountered: