> There's one definite bug: AppWidgetProvider fails to > handle ACTION_APPWIDGET_DELETED actions properly.
Good point, the backend service is sending the wrong extras--fixing that now. Another simple way to fix would be to override onReceive to handle this special-case early before passing to AppWidgetProvider through super. > Additionally (and I haven't investigated this yet) there appears to be a > possible deficiency in the timeliness of ACTION_APPWIDGET_UPDATED > broadcast cessation. Hmm, that seems odd. It might be related to how updates are scheduled; what interval are you using? Widget updates are handled using the new AlarmManager.setInexactRepeating(), which can help save battery, but can be a little unpredictable. > The image is not requested again. What is causing > this, over-aggressive optimization in the handling of RemoveViews by the > widget framework, or something else? It might be an optimization in ImageView, since it already has that Uri loaded. It might be enough to have two RemoteView actions, one to unset it and another to set it back. > (Again the workaround is simple: decorate the Uri with something distinctive > like a timestamp so that the Uri is unique on each request.) That sounds like a good solution too. -- Jeff Sharkey [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
