Collections can now go where you put them on Home. Sideload over 1.0.5; the
About screen prints 1.0.6 (8).
If you are coming from 1.0.4 or earlier, read the 1.0.5 notes as well —
they carry the collections rewrite and the settings audit, and there is a data
warning in them about collections you built by hand.
The switch that could not do what it said
Pin above catalogs did nothing of the kind. Every collection rendered after
every catalogue, so pinning one reordered collections among themselves and
moved nothing past a catalogue. The label had been promising something the code
could not do.
Checked against the Android source rather than guessed: it builds its home rows
by adding each pinned collection first, ahead of the ordered catalogue keys.
Their own wording is exact — "Show this collection above all regular home
catalogs. Multiple pinned collections follow collection creation order." That is
what happens here now, and a pinned collection also takes the opening focus,
since it is what leads the screen.
The default is unchanged and was already correct: with nothing pinned,
collections follow the catalogues on both platforms. So "my collections are at
the bottom" was only ever a bug once you had pinned one.
A collection is a home row now, not an afterthought
The deeper half. Upstream keeps one ordered list in which a collection is an
equal of a catalogue, so it can sit between any two of them rather than only at
one end. Here it could only be top (pinned) or bottom (everything else).
Settings → Sources → Catalog order now lists collections alongside
catalogues, and you can move one anywhere. Three rules came across with it, and
none of them is guessable from outside:
- A row you never moved belongs at the end. One you moved belongs exactly where
you put it. A saved position pointing at an uninstalled addon or a deleted
collection is dropped rather than left as a gap. - With Follow addon order on, a saved catalogue order is ignored — you have
said the addon publishes the order — and only collections move. - In that same mode, a collection is pushed out of the middle of one addon's
run of catalogues. Dropped between two of Cinemeta's rails it would split
them, which is the one thing that mode exists to prevent. Between two
different addons is a boundary rather than a split, so it stays.
Renaming and hero nomination are not offered for a collection row — it is named
in its own editor and cannot be a hero source — and a pinned collection is not
listed there at all, because pinning has already decided where it goes.
Under it
The catalogue ordering and the home row ordering are now one function
instead of two. They had been separate implementations of the same rule, and the
thing that must not drift between two implementations is which rail comes first.
Your existing catalog-order.json is read unchanged; the new field is absent
from it, which is correct.
Verification
129 unit tests and 8 UI tests pass. Thirteen of them are new and cover the merge
and the block normalisation directly, including the case where moving one
collection leaves the next one mid-block and the pass has to run again.
Unchanged from 1.0.5: the Trakt, TMDB and debrid network paths, and the Android
collections round trip, are not verified here for want of the accounts.
Sideloading. Unsigned. Sign it with your own certificate and install with
Xcode, Sideloadly or your usual tool. Requires tvOS 17 or later.