The method of setting the 'originalWidth' and 'originalHeight' runs on a setTimeout (which incidentally also runs continuously when a zoom view is loaded). The method is called grabZoomSubjectOriginalMeasurements
For the first couple of timeouts, the original width and original height are being set to 0, which has the effect of throwing out the zoom when you pinch from a corner within the first couple of seconds.
Since I am running this in full screen, I removed the timeout and changed the method to the following:
This solves the problem completely for my use case.
However, a better approach is needed. One nicer way would be to accept the originalWidth, originalHeight, x and y as parameters, and if so, don't run the timeout.
This looks interesting. I'm particularly interested in the setTimeout running continuously as well – that doesn't seem right. Would you be open to collaborating on a PR to fix this?
Hey,
The method of setting the 'originalWidth' and 'originalHeight' runs on a setTimeout (which incidentally also runs continuously when a zoom view is loaded). The method is called grabZoomSubjectOriginalMeasurements
For the first couple of timeouts, the original width and original height are being set to 0, which has the effect of throwing out the zoom when you pinch from a corner within the first couple of seconds.
Since I am running this in full screen, I removed the timeout and changed the method to the following:
This solves the problem completely for my use case.
However, a better approach is needed. One nicer way would be to accept the originalWidth, originalHeight, x and y as parameters, and if so, don't run the timeout.