Also not sure what you are talking about, but generically, from code, if you want a Drawable object that can be modified, I had that problem. I used a StateListDrawable.
http://code.google.com/android/reference/android/graphics/drawable/StateListDrawable.html It was for Drawables in an ImageSpan. They started out as default placeholder drawables while the Bitmap was loading from the network. After the image came back from the network the handler called addState on the StateListDrawable with the new BitmapDrawable to be displayed, and called setState on it. The problem was it didn't measure right afterwards so I had to re call setText on the TextView passing it the Spanned holding the Drawable that had been updated. Then it worked great. On Dec 5, 9:57 am, pjv <[EMAIL PROTECTED]> wrote: > Just making sure we are talking about notifications (and icons > therein) at the top of the screen? > > From what I recall, the way notifications work is that you can refresh > them in place by sending out a new notification with the same id. > Ofcourse this would give you a chance to update the icon too. Can't > remember how this is done exactly, but look at any basic notification > examples or my Android's Fortune app's source code (which refreshes > the fortune cookie that is offered as a notification). > > Is this simply what you wanted or am I not understanding you? > > On 1 dec, 02:28, Kyle <[EMAIL PROTECTED]> wrote: > > > bump --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
