10-09-2013 01:39 PM - edited 10-09-2013 01:48 PM
Come one Ekke stop trying to wriggle out.
Your blog clearly states you thought it was going to time out, no mention is made of having to tap outside the Toast within the blog entry.
If you are in a ListView with a full set of items and show a toast like this, the ListItem will trigger (i.e. not intended work flow), come on now, honestly do you not think this behaviour can be improved?
Yes all of these things can be worked around but it's better to fix at source.
[Edit] Nice work on the conference app BTW.
[Edit 2] And if that item selected to timeout the toast happens to be the one you are deleting and you haven't got your thread mutexs and code protected it's going to crash!
10-09-2013 02:05 PM
there's no easy answer
on a keyboard device where UNDO is important,
if the user knows the keys to follow his workflow
and he sees the toast and types the next action
then I'm canceling the toast so it disappears immediately
but if nothing happens, the toast should be there to be sure the user knows about
what I don't like: if user then does anything else then clicking the UNDO -
the Toast should immediately disappear and not after some time -
that's the reason I cancel the Toast in these scenarios
but this doesn't work always
10-09-2013 02:53 PM
10-18-2013 05:27 AM
I spent some time deliberating on whether to enter a ticket and in the end decided to go ahead.
Whatever way you look at it, it is duplicating behaviour of another UI element (the dialog) and is a poor design choice better rectified at the OS level rather than worked around or ignored by developers.
If you'd like to upvote it's here...