On Sun, Aug 1, 2010 at 6:26 AM, { Devdroid } <[email protected]>wrote:> You are right, but we are taliking now about non existing feature so that > could also be addressed. The major problem is that notify() is quite > non-flexible recently and forces developers to create bunch of static > icons (which takes memory and bloats apk - I could drop my app size > by at least 100K if that would be possible) instead of allowing them to > draw someting and pass that object. > Oh good lord. My point is: you are relying on another app being around, when you have no guarantee that it will be. What if the app disappears while in the middle of posting the notification? What if it gets removed while you are in the middle of running? Keeping apps fairly self-contained is a good thing. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
