Text Minikernel

[orange808]

Could you add some information about the "free" variables you used in the DPC+ kernel to the first post? Explaining the trade off could save a dev some headaches later.

 

 

DPC+ is desperately low on vars; many devs are going to see the memory map and grab those two extra variables.

[+Karl G]

Documentation has been updated, and the Multisprite kernel example has been updated to no longer include a patched multisprite_kernel.asm file. This was needed due to a bug in the Multisprite kernel which has since been corrected in newer bB releases.

 

No code changes otherwise in this update, so no need to update to the latest version if you are already using this.

[+Gemintronic]

I thought I saw that you posted about having your own score related code in there (5 digit score topic).

 

Does this effect people who use modied score_graphics.asm?  I know I needed to modify that to include A-F and something else for RevEngs multi kernel framework.

[+Karl G]

3 hours ago, Gemintronic said:

I thought I saw that you posted about having your own score related code in there (5 digit score topic).

 

Does this effect people who use modied score_graphics.asm?  I know I needed to modify that to include A-F and something else for RevEngs multi kernel framework.

My duplicate score code is the 6-digit routine that is normally part of the kernel (standard kernel, multisprite, or DPC+). The score_graphics.asm code is not affected, and you can use that version. I actually include a version of RevEng's score_graphics.asm modified to add a "squish" score font (less scanlines used to save CPU cycles).

[+Karl G]

Updated the code and the documentation and example to allow a non-black background color for the text area if the constant "textbkcolor" is set.

[Gateway]

Thanks for doing this, Karl! 😎