eric-ja

There are 4 main code areas that deal directly with screen memory: **1. Pattern fill/blitting** - Blitting from screen (dhgr_get_srcbits) - Fill/blit to screen (dhgr_shift_line, dhgr_fill_line, SetPattern) **2. Text drawing**...

@eschaton The goal is not just the API but a complete understanding of the code and a basis for further dev work. We do have some official docs and headers...

@mgcaret I've got the MGTK disassembly to the point where it makes sense to package it up as module/library, being generally useful to DA's and apps besides DeskTop, as well...

Thank you! Great info. Due to the size of MGTK, I was thinking of building it as a .lib, that way programs would get what they need. Could also be...

Can you post a link to the catalyst font? I'll give a go at converting it.

Here's the catalyst font in MGTK format - use it in place of a2d.font (or whatever). It's nice but noticeably less space-efficient. [catalyst.font.zip](https://github.com/a2stuff/a2d/files/15070973/catalyst.font.zip)

Oops! Some of the chars are 9 pixels wide, which requires that the MGTK font be structured as double-width. Try this one. [catalyst-dw.font.zip](https://github.com/a2stuff/a2d/files/15103103/catalyst-dw.font.zip)

I didn't see anything that was obviously a kerning table in the file xandark uploaded. It could be hard-coded in the catalyst code (haven't looked at all at that.)