stackotter

I'll test locally while waiting for CI, then merge if all goes well.

Damn, merging in the changes from main caused WinUIBackend compilation to fail. It appears to be because I moved the implementation of naturalSize to a static method for convenience when...

And while testing on Windows I found that the graphical calendar view lets you unselect your selection without selecting anything else. I think in that case we should just programatically...

Will merge once CI finishes (it got re-triggered because I had to resolve a merge conflict)

Actually, I just realised that we should have the original init with some fallback implementation and a deprecation warning. I'll do that now.

I created a basic [Quick Start guide](https://stackotter.github.io/swift-cross-ui/documentation/swiftcrossui/quick-start) a few days ago, which is a start but not a proper usage tutorial yet.

Yeah we need to require that elements are Identifiable. It’s been on my todos for a little while. Otherwise there’s no way to assign the child views sensible identities.

Unfortunately we don't support Canvas yet, but we do support Path and Shape. To make an audio visualiser I'd create a custom that returns a path representing the visualisation. The...

> So, could Swift Cross-UI, while maintaining your cross-platform vision, enable rapid progress dedicated to Windows by adding WinUI-specific methods? > > For example, I want to obtain support for...

I'm currently working on a few features that should make platform-specific modifications much easier to perform. I'll be introducing a family of `View.inspect` modifiers for each backend that can be...