EditText is not easy to support as a RemoteView, mostly because of how Home works. Handling its focus and touch events correctly is not an obvious task and we preferred to get it right later than risk it now. It would also become an issue if other apps started to support RemoteViews and did it incorrectly.
When something missing seems obvious and easy, it probably isn't :) On Fri, Apr 17, 2009 at 7:03 AM, Zach Hobbs <ho...@helloandroid.com> wrote: > > In 1.5 many widgets could use EditText (ala Google Search "widget"), > but unfortunately EditText is not a @RemoteView. My initial thinking > is that EditText fields should require a "submit" Button/ImageButton. > So the procedure for getting a value from an EditText: > > - init your RemoteViews > - call a method like for each EditText: RemoteViews.attachEditToButton > ( int edit_text_id, int button_id, String extra_key) > - setup your Button's PendingIntent via > RemoteViews.setOnClickPendingIntent(...) > - now, when your Button is clicked, the Strings from any EditTexts > attached to it would be added to the Extras for the Button's Intent > using the Extra Key supplied in attachEditToButton(). > > Any thoughts or pitfalls? Seems like this would be fairly easy to > implement. > > Thanks, > Zach > > > -- Romain Guy Android framework engineer romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
