> Why there is no read methods in NotificationManager? > > Because an app can keep track of its own notifications, and an app > should not have access to other apps' notifications. >
"Because an app can keep track of its own notifications"... It's not an answer. You can keep track of everything you did, but somehow you have get methods almost everywhere. I don't want to have access to other apps notifications (in fact I want, but I understand why it's forbidden) But I don't really see any reason why NotificationManager.notify/cancel/cancelAll return void and not giving any indication my notifications. It's looks like a poor design for me. > > > Is it on purpose? > > Most likely. > > > Will it be added in future releases? > > You will find out when the rest of us find out, when future releases > are released. > > > If not, maybe somebody know how to get Intent object out of > PendingIntent? > > There is no API for that, sorry. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.7 Available! > -- 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
