I've had a user say that one of my toasts never left the screen even after
exiting the app. Has anyone else had a stuck toast?
--
Writing code is one of few things
that teaches me I don't know everything.
http://www.fuligin.com
--
You received this message because you are subscribed to the G
I had a similar issue because of using Toast.LENGTH_LONG. Try reducing the
duration.
If you use the LENGTH_LONG and then the user switches to home screen
immediately after the toast came up, I guess it will continue to be on the
screen until it times out.
Maybe you can test it with Toast.LENGTH_SHO
I'll switch them to short and see if that works. This guy was claiming
that it didn't leave until he rebooted the phone. That sounds like a bad
deal to me. I rely on the toasts to give information but I may just switch
it out and show it in a custom area. I've got great plans but getting
th
Are you able to recreate the exact problem mentioned by the user?
Try to see what is happening in the logcat at that point when the toast
refuses to go away.
On Tue, Nov 17, 2009 at 11:26 AM, Wayne Wenthin wrote:
> I'll switch them to short and see if that works. This guy was claiming
> that i
I haven't had a chance to try to reproduce it. I'm hoping to have him give
me more information on the phone and the current os version.
On Tue, Nov 17, 2009 at 9:32 AM, Aniruddh Bajirao wrote:
> Are you able to recreate the exact problem mentioned by the user?
> Try to see what is happening in t
No stuck toasts here. As documented, you generally don't have to
cancel them as they expire after the time you set, but there have been
cases I've wanted to dismiss them sooner than the timer (depending on
user actions), In the main UI thread you can call
myInstantiatedToast.cancel();
Has to be i
6 matches
Mail list logo
