Swift4ã®KVOã«æ–°ã—ã„クãƒãƒ¼ã‚¸ãƒ£é–¢æ•°ãŒå°Žå…¥ã•ã‚Œã¾ã—㟠- Qiita
// observeã®çµæžœã‚’æ ¼ç´ private var keyValueObservations = [NSKeyValueObservation]() // UIScrollViewã®ç§»å‹•ã‚’感知ã—ã¦closureを実行ã™ã‚‹ private func addKVO(scrollView: UIScrollView, _ closure: @escaping ()->Void) { let keyValueObservation = scrollView.observe(\.contentOffset, options: [.new, .old]) { _, change in if change.newValue == nil { return } closure() // ã‚ーボードを消ã™ã¨ã‹ãƒ»ãƒ»ãƒ» } keyValueObservations.append(keyValueObser
KeyPathã®ä¾¿åˆ©ãªä½¿ã„é“ã‚’ç ”ç©¶ã™ã‚‹
KeyPathã®ä¾¿åˆ©ãªä½¿ã„é“ã‚’ç ”ç©¶ã™ã‚‹ - KVO以外ã«KeyPathã®æ´»ç”¨æ–¹æ³•ã¯ã‚ã‚‹ã‹ - NSPredicateã®æ”¹å–„ - Lens?
Exploring KVO alternatives with Swift
Swift has access to all of the Objective-C APIs, which means that anything you could do with Objective-C you can now do with Swift. However, there are times when it is worth exploring a better, pure-Swift, alternative. This post explores the pros and cons of KVO versus a couple of Swift alternatives. A recent blog post by Ash Furrow made a really interesting point: Pay attention to the friction yo
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}