andrew/libakgl
1
0
Fork 0
Code Issues 67 Pull Requests Actions Packages Projects Releases Wiki Activity

akgl_TilemapLayer does not record a layer's name #41

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

Source: TODO.md, "Found while writing the manual" -> "Defects with no prior entry", item 6 (at bbb7b8f)

akgl_tilemap_load_layers reads id, opacity, visible, x, y and type
and drops the name Tiled wrote. The only name retained anywhere is
per-object.

A game therefore cannot ask for "the terrain layer" and must hard-code a numeric
layer id, which changes whenever somebody reorders layers in the editor. Both
tutorials hard-code one.

Adding the field is an ABI break, so it wants to land with other tilemap changes
-- most obviously the footprint refactor, which rewrites the layer struct anyway.

Files: src/tilemap.c (akgl_tilemap_load_layers), include/akgl/tilemap.h

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

**Source:** TODO.md, "Found while writing the manual" -> "Defects with no prior entry", item 6 (at bbb7b8f) `akgl_tilemap_load_layers` reads `id`, `opacity`, `visible`, `x`, `y` and `type` and **drops the `name` Tiled wrote**. The only `name` retained anywhere is per-object. A game therefore cannot ask for "the terrain layer" and must hard-code a numeric layer id, which changes whenever somebody reorders layers in the editor. Both tutorials hard-code one. Adding the field is an ABI break, so it wants to land with other tilemap changes -- most obviously the footprint refactor, which rewrites the layer struct anyway. **Files:** `src/tilemap.c` (`akgl_tilemap_load_layers`), `include/akgl/tilemap.h` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.10.0 milestone 2026-08-02 18:33:25 -04:00
tachikoma added the api-gapabi-breakblast-radius:medium labels 2026-08-02 18:33:25 -04:00
tachikoma added the status::grooming label 2026-08-02 18:49:20 -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
Header comments, manual, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a number in PERFORMANCE.md 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 abi-break api-gap blast-radius:medium status::grooming
Milestone
No items
No Milestone 0.10.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/libakgl#41
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?