Her sprit was weak, but knew the work of her hands.
Fixer, weaver, lover, spy. (🔞)
| 🏳️🌈 | ⚧ ⚢ ⚤ ♡∞ |
| Pronouns | she/her |
| Web | https://millenomi.name/ |
| Header | https://unsplash.com/photos/8gPev-y29WQ |
Her sprit was weak, but knew the work of her hands.
Fixer, weaver, lover, spy. (🔞)
| 🏳️🌈 | ⚧ ⚢ ⚤ ♡∞ |
| Pronouns | she/her |
| Web | https://millenomi.name/ |
| Header | https://unsplash.com/photos/8gPev-y29WQ |
And of course, neither of these approaches produces a traditional Mac settings/preferences panel, so for there it has to be rewritten to use TabView.
You _could_ ship a NavigationSplitView there, but I find that System Settings is a terrible experience all around, one that justifies itself out of sheer density and navigation depth; if you don't have that, a settings panel is a much better way to go, IMO.
Unfortunately, this targets iOS 18, where NavigationSplitView is basically broken across a range of basic adaptations.
So I rewrote it as a NavigationStack for there. Still some breakage (note the back button), but usable.
It's sparse, and it used to be just a single .grouped Form with sections, but it looked ugly as heck. But to do it right I had to write its structural harness three times.
Once 'the right way'; on iOS 26, NavigationSplitView works correctly across idioms and adaptations, and so we can just use that.