Bug 11217 - ViewPager method argument names are generic and do not match Android SDK names
Summary: ViewPager method argument names are generic and do not match Android SDK names
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.8.x
Hardware: PC Mac OS
: Low major
Target Milestone: ---
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2013-03-17 22:16 UTC by t9mike
Modified: 2013-06-27 09:31 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description t9mike 2013-03-17 22:16:52 UTC
For example, void SetCurrentItem (int p0, bool p1)
Comment 1 Miguel de Icaza [MSFT] 2013-05-22 15:48:42 UTC
For cases like this, we should try to fix these names, since it would allow better use of our C# named parameters feature.
Comment 2 Atsushi Eno 2013-05-27 23:39:02 UTC
This won't happen until we release a major version-up release *that can break API compatibility*.
Comment 3 t9mike 2013-05-28 09:34:50 UTC
I doubt many customers are using named parameters with existing p0, etc. arguments. Why would someone? They are cryptic.
Comment 4 Atsushi Eno 2013-05-28 10:27:42 UTC
I don't care about parameter name changes, but it's not (only) about parameter names but about *type* names which are used in generated *EventArgs*. They do break ABI compatibility significantly.
Comment 5 Atsushi Eno 2013-06-27 09:31:55 UTC
We ended up to bring those parameter names in support-v* bindings. The binding keeps ABI-compatibility members with [Obsolete] attribute to not break API.

It will be available in the next alpha version.