|
|
Re: Changing topic... playch10.cpp question
01/28/18 06:01 AM
|
|
|
> Surely the issue here is not the porting to the artwork system, but the fact that the
> driver doesn't seem to support that display ticking down outside of the data writes?
> Unless I've misunderstood and the BIOS has to keep writing updated values to that for
> it to work. If it didn't, then you'd want code like this instead of the popmessage,
> then you can have artwork for digit0 to digit3 to do the job.
>
> for (i=0; i<4; i++)
> {
> output().set_digit_value(i,m_timedata);
> }
>
> There's probably some argument about what actually drives that display as well, but
> since I'm thigh deep in an attempt to rebuild and improve my development/playing PC,
> I can't actually run anything to test it, so there are caveats with using this
> directly.
- There's no need to set every digit when only one's written
- set_digit_value is horribly inefficient, and I plan to kill it with fire at some point
- There's a BCD decoder in the path so you have to map values
|
|
Index 
Flat 
Re: Changing topic... playch10.cpp question
Reply
asteroid.cpp question...
