Preview 13

CharSequences

In response to user feedback, we have implemented a new approach to binding thejava.lang.CharSequence interface exposed by Android. Most of the Android API is exposed asCharSequences instead of java.lang.String to support formatted text. SpannableString and SpannedStringare a couple of CharSequence implementors exposed in Android.Text to support this capability.

Our new binding approach is to produce an overloaded API. Where the Android API exposes methods withCharSequence parameters, we provide overloaded methods for string and Java.Lang.ICharSequencevariants of the method signature. For properties and methods with CharSequence return values, we had to create alternatively named elements. For example, Android.Widget.TextView now has "overloaded"TextView.Text and TextView.TextFormatted properties:

public string Text { get; set; } 
public Java.Lang.ICharSequence TextFormatted { get; set; }

This means that you can now do things like:

EditText editText = new EditText (this);  
...
string text = editText.Text;

without have to use Convert.ToString() or object.ToString() to get a string value as with the previousIEnumerable<char> implementation. However, if you want to set or manipulate formatted text in the view, you will have to use the TextFormatted property now.