Pelaa 1.0.16

Released: 28 August 2026 (build 41)

A bug-fix release about empty rows. Coaches on 1.0.15 still saw rows they never made, and deleting them made more of them. That turned out to be two separate faults that look identical from the bench, one on the Track and one inside a Stack. Both are fixed.

A row you delete stays deleted

Delete an empty row on the Track and it came back the moment you touched anything else. Attach a label, edit a tag, open a Stack: the next redraw brought every row you had just deleted back at once. Delete three, attach one label, all three return together.

A row can be held open behind the scenes while a toggle is running, so the tag being recorded has somewhere to live. The delete removed the row but not the hold, and the next redraw honoured the hold and drew the row again. The delete now takes the hold with it, and undo hands it back, so undoing that delete still works.

A button that could not record its tag no longer stays lit

If a press was refused, the button stayed active and its row stayed held for the rest of the session. Nothing you clicked afterwards would clear it. A refused press now closes itself, in every path that can refuse one, including the ones that ran when you cut all running tags at the end of a period.

Labels no longer make rows

A label attaches information to a tag. It is not an event and it never should have had a row of its own. Pressing one through a link could still create one. It cannot now.

Empty rows inside a Stack, multiplying

A saved project could hold the same Stack row four times, exact copies down to the timestamp. The Stack drew them as one row, so nothing looked wrong on screen while the file kept doubling on every save.

Restoring a row after a delete could write a second copy of a row that was already there. Writing a row is now a single action no matter how many times it is asked for, and the same goes for clips inside a row.

Projects that already carry the copies repair themselves on opening. Every Stack in the project is repaired, not only the one you happen to have open, so the next save writes the whole file clean. Nothing to re-import, and no clip is lost.

Thanks

Both of these came from a coach who kept reporting the same symptom after two releases had claimed to fix it. Sending the project file itself is what made the second one findable. If something in Pelaa is wrong for you, the file is worth more than a description of it: [email protected].