akgl_UiAnchor has no top-centre or bottom-centre anchor #79

New Issue

tachikoma · 2026-08-02T19:04:57-04:00

tachikoma commented

2026-08-02 19:04:57 -04:00

Source: filed from akbasic's TODO.md §7, which recorded it and deliberately did not file it (at 9151438)

akgl_UiAnchor has the four corners and dead centre, so a HUD label can be placed at five
positions. A top-centre or bottom-centre anchor is the obvious sixth and seventh and does not
exist.

Those are the two positions a game actually wants for the things a HUD is usually made of: a score
across the top, a status line across the bottom.

Closing it is two appended enum values and two arms in akgl_ui_label()'s switch (src/ui.c),
using the CLAY_ATTACH_POINT_CENTER_TOP and ..._CENTER_BOTTOM constants the dialog helper in
the same file already uses, with the horizontal inset dropped.

Appending keeps 0 through 4 meaning what they mean, so it is additive rather than an ABI break
on the enum -- though it adds public surface, so it carries the soname either way.

Why it arrived here from a consumer rather than as a feature request. akbasic's BASIC HUD
verb exposes exactly the anchors this enum has, so the five it offers a program are five because of
this file. Its TODO recorded the gap and then declined to file it, on the grounds that "changing a
dependency submodule is that repository's decision, not this one's" -- which is the right instinct
about changing it and the wrong outcome for reporting it. Filed here now so the decision can be
taken where the code is.

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

**Source:** filed from `akbasic`'s TODO.md §7, which recorded it and deliberately did not file it (at 9151438) `akgl_UiAnchor` has the four corners and dead centre, so a HUD label can be placed at five positions. **A top-centre or bottom-centre anchor is the obvious sixth and seventh and does not exist.** Those are the two positions a game actually wants for the things a HUD is usually made of: a score across the top, a status line across the bottom. **Closing it is two appended enum values and two arms in `akgl_ui_label()`'s switch** (`src/ui.c`), using the `CLAY_ATTACH_POINT_CENTER_TOP` and `..._CENTER_BOTTOM` constants **the dialog helper in the same file already uses**, with the horizontal inset dropped. **Appending keeps 0 through 4 meaning what they mean, so it is additive** rather than an ABI break on the enum -- though it adds public surface, so it carries the soname either way. **Why it arrived here from a consumer rather than as a feature request.** `akbasic`'s BASIC `HUD` verb exposes exactly the anchors this enum has, so the five it offers a program are five because of this file. Its TODO recorded the gap and then declined to file it, on the grounds that "changing a dependency submodule is that repository's decision, not this one's" -- which is the right instinct about *changing* it and the wrong outcome for *reporting* it. Filed here now so the decision can be taken where the code is. --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)

tachikoma added this to the 0.10.0 milestone 2026-08-02 19:04:57 -04:00

tachikoma added the api-gap blast-radius:low status::grooming labels 2026-08-02 19:04:57 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: andrew/libakgl#79