Bug 3992 - UIScrollViewDelegate WillEndDragging gives nonsensical values for targetContentOffset
Summary: UIScrollViewDelegate WillEndDragging gives nonsensical values for targetConte...
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.2
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on:
Blocks: 4368
  Show dependency tree
Reported: 2012-03-20 14:41 UTC by Chris Toshok
Modified: 2012-04-10 13:22 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Chris Toshok 2012-03-20 14:41:20 UTC
mind you, I couldn't find docs/samples/blogs about what the values *should* look like, but these values passed to the method look sane for velocity, and insane for targetContentOffset:

velocity = {X=0, Y=0.7103275}
targetContentOffset = {X=-1.998565, Y=3.629363E-43}

that was for a sizable vertical flick of my thumb, so I'm not sure 1) why there's any targetContentOffset registered (the X velocity is 0), and 2) why the Y offset is so low.

marshaling/binding problem?
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-03-21 20:14:43 UTC
It definitively looks like a marshaling problem.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-03-27 09:32:23 UTC
It was a marshaling problem.

Fixed in master (47ac894) and 5.2-series (13c33ae).

The next releases with this fix will be 5.2.11 and 5.3.3.