Timothy Moose
Timothy Moose
I took a look and found a couple of issues: First, `KeyboardTrackingView` is based on notifications. If you create a new one after the keyboard has already appeared, it won't...
The idea with the updated `KeyboardTrackingView` is that your view controller needs to create and hold onto a single instance and use that instance for each message. That way it...
Thanks for calling my attention to this.
I wasn't able to reproduce the warnings, but I made some guesses and I think it should be good now. Could you pull down the head of `master` and let...
@jmarr I appreciate the detailed writeup. I'm unlikely to look at this anytime soon given that it is an obscure problem and you have a workaround. Hopefully it will resolve...
Bro. Why aren't y'all using Factory yet
@kalebzen instead, would you be willing to wrap your instance in this? ````swift class MainActorBox { init(instance: @escaping @autoclosure @MainActor () -> T) { self.factory = instance } @MainActor var...
@kalebzen I noticed the striking header in doc center seems broken lately. Ya'll should check out our new library – I think it could fix that and eliminate a lot...
@kalebzen The box type I gave you would be returned by resolver without any need for main actor context. You would only need to be in a main context when...
Sample project: [MainActorBox.zip](https://github.com/SwiftKickMobile/SwiftMessages/files/14388577/MainActorBox.zip) I removed the `@autoclosure` from `MainActorBox` because the compiler was yelling at me and I didn't want to spend time figuring it out.