stackotter

Results 169 issues of stackotter

I don't really know how SwiftUI detects when preference values have changed, given that they aren't required to be equatable. Things are declarative so we can't just listen for a...

bug

At the moment the force casts and force unwraps print relatively generic messages when they cause fatal errors. We should probably replace the force casts and force unwraps with helper...

enhancement

Currently, if you close a window, there's no way to reopen it. We should support each platform's usual windowing controls. E.g. on macOS window groups get added to the `Window`...

enhancement

At the moment SwiftCrossUI doesn't even try to listen for window close events. This leads to it trying to update properties of closed windows which can cause crashes under some...

enhancement

The docs should have images demonstrating what the various views look like across the supported backends. And we should do a similar thing for view modifiers as well where applicable.

documentation

Whenever I perform a clean release build of a SwiftCrossUI project, it takes way longer than it should. There are a few places it often seems to get stuck; 1....

enhancement

bug
UIKitBackend
layout

At the moment, AppKitBackend encodes all of its layout decisions as constant layout constraints (with exact pixel values). This is probably a bit inefficient, but more importantly, it doesn't interact...

enhancement
AppKitBackend

This PR introduces various APIs related to improving interoperability between SwiftCrossUI view code and native UI frameworks. This includes: - Making it easier to make platform-specific modifications to the native...

This is a tracking issue for Android support. I've started some work locally but haven't published any of my progress yet. I've mostly been trying to figure out the bundling...