Bug 3414 - Make the Intent.Data property writeable
Summary: Make the Intent.Data property writeable
Status: RESOLVED DUPLICATE of bug 1725
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.0
Hardware: All All
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-02-12 17:09 UTC by Mike Bluestein
Modified: 2012-02-13 02:01 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 DUPLICATE of bug 1725

Description Mike Bluestein 2012-02-12 17:09:12 UTC
Intent has a SetData method that takes a Uri and a Data property that is read only, which returns a Uri. Instead of (or in addition to) the SetData method, make the Data property writeable.
Comment 1 Atsushi Eno 2012-02-13 01:29:52 UTC
It is by design. In Java Android, setData() is not a setter that we convert to property. Our property conversion process expects the setter to not return anything. However, like a typical fluent API, setData() returns the Intent itself and like JavaBeans is not compatible with fluent API, our property conversion is not compatible with this kind of API.
Comment 2 Atsushi Eno 2012-02-13 02:01:04 UTC
Actually I found a duplicate that still expects solution.

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