title: Android Toast Cancelled But Not Dequeued
body: <p>I am using a single Toast object that is being accessed from multiple methods. Each of the methods initializes the Toast to display a different message, and each of the methods cancels the existing Toast on the screen in order to display its own. However, after the on-screen Toast is cancelled and it disappears, there is a delay before the new Toast is displayed. </p>
  
  <p>I have found that this delay is exactly equivalent to how long it would have taken the original Toast to disappear off the screen by itself (instead of being cancelled). This has led me to believe that although the Toast cancel() method removes it from the screen, it does not dequeue it from the system, causing other Toasts to still have to wait before they are displayed. Is there any way around this?</p>