Bug 5584 - Missing Button.SetText(Span [html]) signature
Summary: Missing Button.SetText(Span [html]) signature
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-06-08 15:33 UTC by Ian
Modified: 2012-06-08 15:57 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 Ian 2012-06-08 15:33:13 UTC
I'm trying to set a Button's text with Html.FromHtml("some html") 

In Java this works:

myButton.setText(Html.fromHtml("<small>(sub comment)</small>")); 

But in Mono for Android that fails as there is no signature in SetText that accepts the Html.FromHtml span.

Is there another way this is supposed to work?
Comment 1 Jonathan Pobst 2012-06-08 15:57:26 UTC
First, we made all of Java's getXXX and setXXX into C# properties, so in general, you do this:

myButton.Text = "Hello";

but we couldn't make it accept formatted strings as well as regular strings, so we had to add a second property that takes formatted strings:

myButton.TextFormatted = Html.FromHtml ("<small>(sub comment)</small>")

It's not ideal, but it was the compromise that allowed most people (who don't want formatted strings) to work in a sensible way, while still providing a way to use formatted strings.

Hope this helps!