I don't know the priorities of the android team but to me this looks like a really significant bug.
As reported here: http://code.google.com/p/android/issues/detail?id=2539&q=Widget&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars and here: http://code.google.com/p/android/issues/detail?id=3696&q=Widget&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars and a few other places in different wording. Apart from it not working anything like the documentation specifies, it disables two methods in the widget provider class, creates potentially huge redundancies/wasted cpu usage and pretty much makes any widget that uses a config activity a bad piece of software. Further yet, the problem with screen real estate failures (first link, my post) applies to ALL widgets, config activity or not. The entire widget framework is effected by these limbo widgets and it seems like something really small, perhaps a few lines of code to fix, considering you display Toasts and other things, the failure paths are already known, should it not just unbind these widget ids on failure? Also as a small suggestion, considering you know the minimum dimensions of the widgets before they're added, widgets could not even be shown or grayed out if the screen can not accommodate them. I notice the "Add" in the Menu does this but only when the screen is completely full, if there is any space left, a larger widget can still be chosen to add, even though it's guaranteed to fail. Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
