Skip to content

M
Material
Commit 51524eea by Daniel Dahan
Options

issue-886: fixed memory leak with previousNavigationDelegate and previousTabBarDelegate

parent c121c534
Showing with 5 additions and 10 deletions
.gitignore
...@@ -16,12 +16,7 @@ profile ...@@ -16,12 +16,7 @@ profile
*.moved-aside *.moved-aside
*.playground *.playground
*.framework *.framework
Sources/Frameworks/Motion/.git* DerivedData
Sources/Frameworks/Motion/.gitignore Index
Sources/Frameworks/Motion/.swift-version Build
Sources/Frameworks/Motion/CONTRIBUTING.md
Sources/Frameworks/Motion/Motion.podspec
Sources/Frameworks/Motion/Motion.xcodeproj/
Sources/Frameworks/Motion/Sources/Info.plist
Sources/Frameworks/Motion/Sources/Motion.h
Sources/Frameworks/Motion/Sources/Extensions/Motion+UIViewController.swift
...@@ -47,13 +47,13 @@ fileprivate struct AssociatedInstance { ...@@ -47,13 +47,13 @@ fileprivate struct AssociatedInstance {
A reference to the previous navigation controller delegate A reference to the previous navigation controller delegate
before Motion was enabled. before Motion was enabled.
*/ */
var previousNavigationDelegate: UINavigationControllerDelegate? weak var previousNavigationDelegate: UINavigationControllerDelegate?
/** /**
A reference to the previous tab bar controller delegate A reference to the previous tab bar controller delegate
before Motion was enabled. before Motion was enabled.
*/ */
var previousTabBarDelegate: UITabBarControllerDelegate? weak var previousTabBarDelegate: UITabBarControllerDelegate?
} }
extension UIViewController { extension UIViewController {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment