onUpdate being called is a bug, and contradicts what's in the documentation. A widget is created, but won't be shown until after the config activity returns.

The widget ID still being there even if you cancel the config activity is also a bug on some versions of Android.

I documented my workaround for the second bug here:

http://kmansoft.wordpress.com/2010/06/22/per-widget-options-stale-widgets/

-- Kostya

11.02.2011 17:59, Mattias Svala ?????:
As far as I can tell, if I have defined a configuration activity for my widget then onUpdate should not be called when it is first created. It would be the configuration activity's responsibility to perform the initial configuration of the widget.

Why is it then that I still get calls to onUpdate in the widget provider, and after that call the configuration activity is started. If I cancel the configuration activity I get no visible widget on the home screen. If I have cancelled a widget configuration (by pressing back in the configuration activity) and reinstall the APK all the widgets, including the cancelled ones, each gets mentioned in calls to onUpdate.

Surely this shouldn't be so. And if it is, then how do I get rid of the widgets that was cancelled during configuration.

I'm running my code on the emulator with Android 1.6.

:.:: mattias

P.S. I have also posted this question on stackoverflow.com, http://stackoverflow.com/questions/4966839/
--
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


--
Kostya Vasilyev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com

--
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

Reply via email to