This seems to be a design constrant, with the idea of keeping AppWidgetProvider processes in memory as little as possible.
I can see this being useful for regular widget rendering, but loading the process for the one current widget the user is interacting with doesn't seem too bad. Besides, this constraint is already violated by the new scrollable widgets in 3.0, which rely on an application-side service for providing list items. Home screen widgets were introduced in 1.5, two years ago. Have the devices not improved since then? -- Kostya 2011/6/24 String <sterling.ud...@googlemail.com> > On Thursday, June 23, 2011 4:45:40 PM UTC+1, TreKing wrote: > >> On Thu, Jun 23, 2011 at 3:44 AM, String <sterlin...@googlemail.com>wrote: >> >>> "1* Would be 5* if the widgets were expandable, rather than cluttering up >>> my widget picker with 8 different sizes." >> >> >> Can't you disable Widgets such that they don't show up in the Widget >> Picker? >> > > Not directly, though there are ways... But if I can't do a resizable > widget, I'll still need the 4 discrete sizes, so I'm not sure that helps. > > String > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
