Bug 5153 - Standard Controls is not fully implemented for iPad
Summary: Standard Controls is not fully implemented for iPad
Status: RESOLVED DUPLICATE of bug 22753
Alias: None
Product: iOS
Classification: Xamarin
Component: Samples ()
Version: 5.2
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Oleg Demchenko
Depends on:
Reported: 2012-05-17 17:35 UTC by PJ
Modified: 2015-01-14 10:44 UTC (History)
3 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 PJ 2012-05-17 17:35:28 UTC
While Standard Controls covers a bevy of widgets, the iPad version only includes Action Sheets and SimpleDatePicker.

Found on monotouch-samples 125102cae5d7424f11bd95297ca86c346aa8451b (master)

Bryan C is on the README so I'm adding him as the assignee, feel free to re-distribute.
Comment 1 bryan costanich 2012-05-17 21:34:24 UTC
Yeah, i suppose we could add them. the iPad version only contains the controls that are iPad specific.
Comment 2 Paola Villarreal 2014-11-04 11:32:07 UTC
can we close this?
Comment 3 Aaron Sky 2015-01-14 10:44:44 UTC
This is a duplicate of #22753, which has been closed.

*** This bug has been marked as a duplicate of bug 22753 ***