Dianne, thanks for answers. > In fact one of the problems with the API that the task killers have been > abusing is that it was there for the "force stop" button in the UI. This is > not for killing processes. This is for making everything about the app > stop: not just its processes and services, but removing its notifications, > removing its alarms, EVERYTHING.
This is exactly what I had in my mind. My widget has no chance to toast message "Oh, it hurts, I was killed. Please don't do it next time". It just silently stops and looks like it does not work properly. To inform the user that widget was killed I have to develop detection mechanism (as writing this to documentation is not enough for many users). This is extra NON PRODUCTIVE work that every successful widget needs to do. This is why I'm asking for action from Google. > This is why they have such a bad impact on well-behaved applications, and is > something that really needs to be addressed in the platform (it is just not > right for one application to do this kind of thing to another one). Thanks for your opinion. I have the same feeling. Tom -- 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
