Explore >> Select a destination
|
You are here 
|
inessential.com | ||
| | | | |
www.jessesquires.com
|
|
| | | | | A few days ago I was (finally!) updating a project to use Swift 2.2 and I ran into a few issues when converting to use the new #selector syntax introduced by... | |
| | | | |
swiftrocks.com
|
|
| | | | | In this article, we'll explain the concept of type erasure, how it used to be done, what's different in Swift 5.7, and how these changes work under the hood. | |
| | | | |
sintraworks.github.io
|
|
| | | | | Recently I started studying Ray Wenderlich's tutorial book RxSwift. Early on, the book suggests using Rx as an alternative to delegates and their associated protocols. I though, great, but, for the task at hand, that's a rather heavy handed solution. (Yes, I know it is just an example designed to teach me the basics.) So I tried to imagine how I could achieve something similar to the functionality they built for their initial examples, without the overhead of importing a big library like RxSwift. | |
| | | | |
sintraworks.github.io
|
|
| | | In this post we will create a SwiftUI control that can be popped up from the bottom of the screen. We will also make it possible to allow a specific view (usually the view that triggers the control and reflects the chosen value) to be raised, if it would otherwise be obscured by the control when the control pops up. This post assumes you have a reasonable knowledge of SwiftUI and are at least somewhat familiar with more advanced topics such as bindings, geometery readers, preference keys, etc. It won't go into details as to how they work. I will simply show how to use them to achieve the desired effact. | ||
