andrew/akbasic
1
0
Fork 0
Code Issues 27 Pull Requests Actions Packages Projects Releases Wiki Activity

The palette cannot be written, so the era's cheapest animation is a full redraw #17

New Issue
Open
opened 2026-08-02 19:04:23 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 19:04:23 -04:00
Collaborator
Copy Link

Source: TODO.md §4 (at 9151438)

PALETTE[17] in src/graphics_tables.c is static const, and COLOR can only choose among its
sixteen entries.

Palette rotation was the cheapest animation of the whole era -- one register write cycled every
pixel of a colour -- and here the same effect is a full redraw: the demo's title "colour cycle"
re-strokes the logo every frame (DRAWTEXT with CM# = 1), and its raster bars erase and redraw
five ramp lines apiece per frame.

Closing it means: palette state moves from a static table to the graphics backend, plus a verb
form to set an index (COLOR grew nothing new on a C128, so this would be ours -- Chapter 13
material), plus the docs figures that assume Pepto's values stay put.

Files: src/graphics_tables.c, src/graphics_akgl.c, docs/13-differences.md

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md §4 (at 9151438) `PALETTE[17]` in `src/graphics_tables.c` is `static const`, and `COLOR` can only choose among its sixteen entries. **Palette rotation was the cheapest animation of the whole era** -- one register write cycled every pixel of a colour -- and here the same effect is a full redraw: the demo's title "colour cycle" re-strokes the logo every frame (`DRAWTEXT` with `CM# = 1`), and its raster bars erase and redraw five ramp lines apiece per frame. **Closing it means:** palette state moves from a static table to the graphics backend, plus a verb form to set an index (**`COLOR` grew nothing new on a C128, so this would be ours** -- Chapter 13 material), plus the docs figures that assume Pepto's values stay put. **Files:** `src/graphics_tables.c`, `src/graphics_akgl.c`, `docs/13-differences.md` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 1.0.0 milestone 2026-08-02 19:04:23 -04:00
tachikoma added the api-gapblast-radius:mediumstatus::grooming labels 2026-08-02 19:04:23 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Documentation, comments, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a measurement behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label api-gap blast-radius:medium status::grooming
Milestone
No items
No Milestone 1.0.0
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/akbasic#17
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?