Yes, the service is raising the Toast. It's similar (I think) to what the ApiDemo services do. I could use notifications, but I was looking for a quick and dirty way of a simple message in this case (And normally I do). I just never expected that particular error to happen, and I was wondering what could be the cause.
I decided to remove the Toast messages and did some reworking to eliminate the need for them in the first place, so now it's just a curiosity of understanding why it happened. On Dec 29, 1:55 pm, Mark Murphy <[email protected]> wrote: > Alvin Yates wrote: > > I'm using a bunch of Toast messages in my application in order for > > certain services to communicate to the user. The problem seems to be, > > however, that if I navigate certain parts of the app too quickly, one > > of the toast messages never actually disappears, which I think may > > have to do with the instance of the service that called it being > > destroyed prematurely in some fashion. > > A service is raising a Toast? > > Are you sure you aren't better served using Notifications instead? Or > having an activity raise the Toast if your activity is in the foreground? > > IMHO, services should not be directly affecting the UI. > > And if I misunderstood your comment, my apologies. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > > Android Training on the Ranch! -- Mar 16-20, > 2009http://www.bignerdranch.com/schedule.shtml --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
