Pelaa 1.0.15

Released: 27 August 2026 (build 40)

A bug-fix release, and a correction to what 1.0.14 promised. One row name could sit on the Track twice, and the second copy did nothing at all.

One row name, one row

A Track row could appear twice under the same name. Only one of the pair held your tags. The other drew empty, and clicking it did nothing, because there was nothing there to click.

The Track finds a row by its name, so a name it can reach twice is a name it cannot resolve. Every tag landed in the first copy and the second sat there for the rest of the project's life. Deleting it by hand did not help either: the name was still tagged, so the row came back.

Projects that already carry a doubled row repair themselves. Open one in 1.0.15 and you get one row per name, with every tag in it. Nothing to clean up, nothing to re-import, and no tag is lost in the process.

Where the doubled row came from

Combining two projects, or appending one to another, was the way in. A row remembers the colour it was tagged in. When the same button carried a different colour in the two projects, the merge treated them as two different rows and kept both, under one name.

That is closed. A merge now matches rows by name, so appending or combining projects gives you one row per button, in the colour the project you were already working in uses.

Adding a row to an affected project could quit the app

On a project carrying a doubled row, sorting the Track could bring the app down outright. Adding a row, dragging rows into a new order and sending clips to a Stack all sort it. Nobody reported hitting this, and it could not happen simply from opening a file, but it was one click away for anyone whose project had the doubled row. Sorting now handles a repeated name instead of falling over on it.

Correcting 1.0.14

1.0.14's notes said projects carrying stray rows repair themselves on opening. That was true only for a row under a name nothing was tagged with. A row that doubled a name you had tagged survived the repair, so a project could open into 1.0.14 still showing the pair. 1.0.15 is the release that makes that claim true for both kinds.