Just a question: why "optional multiple onUpdate"? El miércoles, 18 de diciembre de 2013 08:06:20 UTC-3, Andriy Tsykholyas escribió: > > I have read Google's App Widgets > guide<http://developer.android.com/guide/topics/appwidgets/index.html> > . > I'd like to clarify the event flow in > AppWidgetProvider<http://developer.android.com/reference/android/appwidget/AppWidgetProvider.html>in > following scenario: > 0) User installed the app which contains a widget > 1) User added widget (W1) of the app to home screen > 2) User deleted that widget W1 > 3) User added widget (W2) of the app to home screen > > As I understand from documentation the event flow must be following: > 1) onEnabled() > optional multiple onUpdate(W1) > 2) onDeleted(W1) > onDisabled() > 3) onEnabled() > optional multiple onUpdate(W2) > > The question: does the framework guarantees that onEnabled() will be > called in 3)? > Or asking it another way: can onUpdate() be called directly after > onDisabled()? >
-- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
