BeamRacer gfx routines - Githubissues

ytmytm commented 3 years ago

GFX routines should work faster with BeamRacer. Replacing rectangle/hline/vline/point/putstring routines like VDC versions should be enough

[x] whole screen moved to bank 7, last 8+8KB (back/front canvas) reserved
[x] one display list always running, sequencing bitmap from front canvas only
[x] ~~code can be larger and spill into $a000-$bf40 in C64 RAM, this space is free~~
[x] first init - clear screen routine with checkerboard (2 byte pattern) - setup display list and fill/copy routines
[x] draw filled rectangles with fill and skip/step
[x] draw hline with fill
[x] draw vline with skip/step using one port to read, other to write (read-modify-write)
[x] draw point
[x] test point
[x] draw string
[x] draw bitmaps

Fix issue #1 before this to make display list persistent

ytmytm commented 3 years ago

font understanding https://www.lyonlabs.org/commodore/onrequest/geos/geos-fonts.html

ytmytm commented 3 years ago

Can't use $a000-$bf40 space for code, a lot of apps will write directly to the bitmap, even BSW flagship programs (geoPaint, geoWrite, geoFont) don't respect the rules. Basically GEOS128-compatible apps should be safe, but they must support both GEOS64 and 128 mode

ytmytm / geos

BeamRacer gfx routines #3