Image is jump/scrolled to top after zooming

[eldhoseelias]

`` import UIKit import Zoomy

class DZImageViewerViewController: UIViewController {

@IBOutlet weak var imageView: UIImageView!
var imageData : UIImage? = nil
override func viewDidLoad() {
    super.viewDidLoad()
    imageView.image = imageData
    imageView.isUserInteractionEnabled = true
    guard let parentView = parent?.view else { return }

    addZoombehavior(for: imageView, in:parentView)
    //addZoombehavior(for: imageView)
   // addZoombehavior(for: imageView, settings: Settings().with(actionOnTapOverlay: Action.dismissOverlay))
}
override func viewWillDisappear(_ animated: Bool) {
    imageZoomControllers.values.forEach{ $0.dismissOverlay() }
}

@IBAction func backButtonAction(_ sender: Any) {
    self.navigationController?.popViewController(animated: true)
}

}

//MARK: - ZoomDelegate extension DZImageViewerViewController: Zoomy.Delegate {

func didBeginPresentingOverlay(for imageView: UIImageView) {
    //        print("did begin presenting overlay for imageView: \(imageView)")
}

func didEndPresentingOverlay(for imageView: UIImageView) {
    //        print("did end presenting overlay for imageView: \(imageView)")
}

func contentStateDidChange(from fromState: ImageZoomControllerContentState, to toState: ImageZoomControllerContentState) {
    //        print("contentState did change from state: \(fromState) to state: \(toState)")
    //You might want to show/hide statusbar here
}

}

[lvnkmn]

Hmm, thats not suposed to happen.

Two questions, to be able to better help you:

• what content mode is your image view in?
• Which iOS version are you trying this in?

[lvnkmn]

also, did you have the same issues when you didn't specify the parent view? This should normally only bee needed when you want the zoom overlay to appear above elements outside of current view controller hierarchy. When the image to be zoomed is not part of the hierarchy that it will be zoomed in, problems like these may occur. This has to do with the way Absolute coordinates are currently calculated.

tldr; if this only happens when specifying 'in: parentView' we might have to improve the absolute coordinate calculation for these cases.

Let me know 🙂

[lvnkmn]

Closing this due to inactivity, feel free to open it if help is needed.