Bug 4049 - UIControl.CancelTracking should allow null event argument
Summary: UIControl.CancelTracking should allow null event argument
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-03-22 20:15 UTC by Adam Kemp
Modified: 2012-03-22 20:27 UTC (History)
2 users (show)

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

Sample project (8.93 KB, application/zip)
2012-03-22 20:15 UTC, Adam Kemp

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 Adam Kemp 2012-03-22 20:15:32 UTC
Created attachment 1560 [details]
Sample project

The documentation for cancelTrackingWithEvent: indicates that nil is an acceptable argument, and this does in fact work (and is useful). The binding for UIControl.CancelTracking does not reflect this. It throws an ArgumentNullException if you give it a null event.

Attached is a sample project to demonstrate the exception and to demonstrate that you can call cancelTrackingWithEvent: with nil. If you long press the button that says "Works" then it just cancels the tracking (the button unhighlights). If you do the same with the "Broken" button then the app crashes.
Comment 1 Adam Kemp 2012-03-22 20:18:21 UTC
Another workaround aside from calling directly (as I did in my example project) is to use CancelTracking(new UIEvent()) rather than CancelTracking(null). It's better than using void_objc_sendMesg_IntPtr, but it's not as good as just passing null.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-03-22 20:27:09 UTC
Fixed in master (fc56dd1f) and 5.2-series (ada3c170).

It will be included in 5.3.3 and 5.2.11.