blocks|key|1261173|text|我的解决方案是在activity中初始化一个Toast。然后在每次单击时更改其文本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261174|Toast+mToast+=+Toast.makeText(this,+"",+Toast.LENGTH_SHORT);
if+(a)+{
++mToast.setText("This+is+a");
++mToast.show();
}+else+if+(b)+{
++mToast.setText("This+is+b");
++mToast.show();
}|code-block|syntax|javascript|1261175|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

My solution was to initialize a single Toast in the activity. Then changing its text on each click.

<pre><code>Toast mToast = Toast.makeText(this, "", Toast.LENGTH_SHORT);
if (a) {
 mToast.setText("This is a");
 mToast.show();
} else if (b) {
 mToast.setText("This is b");
 mToast.show();
}
</code></pre>

blocks|key|1261378|text|如何检查是否已经显示了一个吐司？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261379|private+Toast+toast;
...
void+showToast()+{
+++if+(toast+==+null+%7C%7C+toast.getView().getWindowVisibility()+!=+View.VISIBLE)+{
++++++toast+=+Toast.makeText(getActivity(),+"Toast!",+Toast.LENGTH_LONG);
++++++toast.show();
+++}
}|code-block|syntax|javascript|1261380|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What about checking if a toast is already being displayed?

<pre><code>private Toast toast;
...
void showToast() {
 if (toast == null || toast.getView().getWindowVisibility() != View.VISIBLE) {
 toast = Toast.makeText(getActivity(), "Toast!", Toast.LENGTH_LONG);
 toast.show();
 }
}
</code></pre>

blocks|key|1046362|text|在类似的问题上，穆达尔的解决方案对我来说效果很好--在多次点击button之后，我有各种各样的吐司堆积在积压中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1046363|一个带有不同setText()s和show()的Toast实例正是我要寻找的答案--上一条消息在单击新按钮时立即取消。点亮|1046364|仅供参考，我是这么做的.|1046365|在OnCreate中|1046366|++++final+Toast+myToast+=+Toast.makeText(getBaseContext(),+"",+Toast.LENGTH_SHORT);|code-block|syntax|javascript|1046367|在每个OnClick中|1046368|myToast.setText(R.string.toast1);
myToast.show();|1046369|entityMap^0|V|6|0|6|A|H|6|0|0|1|8|0|0|3|7|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|14|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|L|3|M|5|N|7|18|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|S|3|T|5|N|7|1C|8|@]|D|@]|E|$O|P]]|$1|U|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|V|$]]

Mudar's solution worked beautifully for me on a similar problem - I had various toasts stacking up in a backlog after multiple <code>button</code> clicks.

One instance of Toast with different <code>setText()s</code> and <code>show()</code>s was the exactly the answer I was looking for - previous message cancelled as soon as a new button is clicked. Spot on 

Just for reference, here's what I did...

In <code>OnCreate</code>:

<pre><code> final Toast myToast = Toast.makeText(getBaseContext(), "", Toast.LENGTH_SHORT);
</code></pre>

Within in each <code>OnClick</code>:

<pre><code>myToast.setText(R.string.toast1);
myToast.show();
</code></pre>

blocks|key|1261573|text|我的解决方案是将所有toast引用保存在一个列表中，并在需要时创建一个方法来取消所有引用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261574|private+ArrayList<Toast>+msjsToast+=+new+ArrayList<Toast>();

private+void+killAllToast(){
++++for(Toast+t:msjsToast){
++++++++if(t!=null)+{
++++++++++++t.cancel();
++++++++}
++++}
++++msjsToast.clear();
}|code-block|syntax|javascript|1261575|创建Toast时，请执行以下操作并保存引用：|1261576|Toast+t+=+Toast.makeText(context,+"Download+error:+xx",+Toast.LENGTH_LONG);
t.show();
msjsToast.addToast(t);|1261577|当您需要删除它们时：|1261578|killAllToast();|1261579|您可以像在全局类中创建静态方法一样创建它，并使用它来杀死应用程序的所有吐司。|1261580|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

My solution is to save all toast references in a list and make a method to cancel all them when need it:

<pre><code>private ArrayList&lt;Toast&gt; msjsToast = new ArrayList&lt;Toast&gt;();

private void killAllToast(){
 for(Toast t:msjsToast){
 if(t!=null) {
 t.cancel();
 }
 }
 msjsToast.clear();
}
</code></pre>

When you create a Toast do this way and save the reference:

<pre><code>Toast t = Toast.makeText(context, "Download error: xx", Toast.LENGTH_LONG);
t.show();
msjsToast.addToast(t);
</code></pre>

When you need to delete them:

<pre><code>killAllToast();
</code></pre>

You can create this like a static method in a global class and use it to kill all the toast of the app.

blocks|key|1046727|text|以下是我对这个问题的简单回答：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1046728|首先，在您的活动中创建一个全局Toast对象。|offset|length|style|CODE|1046729|++++private+Toast+example;|code-block|syntax|javascript|1046730|现在，每当您想调用新的Toast消息时，只需执行以下操作：|1046731|if(buttonClicked)+{
++++example.cancel();
++++example+=+Toast.makeText(this,+""+,+Toast.LENGTH_SHORT);
++++example.setText("Button+Clicked");
++++example.show();
}|1046732|这使所有的Toast都集中在一个Toast中，并删除Toast垃圾邮件。这是一个快速粗略的解决方案，所以也许有一种更优雅的方法来完成它。|1046733|entityMap^0|0|F|5|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Here is my simple answer to the problem:

First in your activity create a global <code>Toast</code> object.

<pre><code> private Toast example;
</code></pre>

Now whenever you want to call a new Toast message just do this:

<pre><code>if(buttonClicked) {
 example.cancel();
 example = Toast.makeText(this, "" , Toast.LENGTH_SHORT);
 example.setText("Button Clicked");
 example.show();
}
</code></pre>

This keeps all the Toasts in one central Toast and removes Toast spam. This is a quick rough solution so maybe there is a more elegant way to do it.

blocks|key|1046508|text|我想我找到了一种方法，让吐司消息不会为我排队。我想和大家分享一下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1046509|这部分放在最上面。|1046510|private+Toast+msg;++++|code-block|syntax|javascript|1046511|这部分放在我的setOnTouchListener()中|1046512|if(null+==+msg)
{
msg+=+Toast.makeText("Message+to+user!",+Toast.LENGTH_SHORT);
msg.setGravity(Gravity.CENTER,+msg.getXOffset()+/+2,+msg.getYOffset()+/+2);
msg.show();

//handels+the+stupid+queueing+toast+messages
new+Handler().postDelayed(new+Runnable()
{
++++++public+void+run()
++++++{
++++++++++msg+=+null;

++++++}
},+2000);

}|1046513|这更像是一种黑客行为。但每当有人喜欢我的应用程序的某一部分时，我都会显示一条吐司消息。如果他们疯狂地点击收藏按钮，它就会疯狂地发送敬酒信息。但现在不是了。它将等待2秒，然后将我的toast对象设置为null，并允许它再次显示。|1046514|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I think I found a way to make toasts message not queue up for me. Thought I would share. 

this part goes at top. 

<pre><code>private Toast msg; 
</code></pre>

This part goes in my setOnTouchListener()

<pre><code>if(null == msg)
{
msg = Toast.makeText("Message to user!", Toast.LENGTH_SHORT);
msg.setGravity(Gravity.CENTER, msg.getXOffset() / 2, msg.getYOffset() / 2);
msg.show();

//handels the stupid queueing toast messages
new Handler().postDelayed(new Runnable()
{
 public void run()
 {
 msg = null;

 }
}, 2000);

}
</code></pre>

It is more of a hack than anything. But I show a toast message any time someone favorites a part of my app. And if they go crazy clicking the favorite button it will go crazy with the toasts messages. But not anymore. It will wait 2 seconds and then set my toast object to null and allow it to display again.

blocks|key|1261791|text|在onClick函数外部创建Toast对象，并使用以下代码。它将停止任何现有的Toast并启动最新的Toast。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1261792|Toast+mToast;

public+void+onClick(String+abc)+{

++++if(mToast!=null)
++++++++mToast.cancel();
++++Context+context+=+this;
++++mToast+=+Toast.makeText(context,+abc,+Toast.LENGTH_SHORT);
++++mToast.show();
}|code-block|syntax|javascript|1261793|entityMap^0|1|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Create a Toast object outside <code>onClick</code> function and use the code below.
It will stop any existing Toast and start the latest Toast.

<pre><code>Toast mToast;

public void onClick(String abc) {

 if(mToast!=null)
 mToast.cancel();
 Context context = this;
 mToast = Toast.makeText(context, abc, Toast.LENGTH_SHORT);
 mToast.show();
}
</code></pre>

blocks|key|1261907|text|·通过Extension+Function实现Kotlin+Version|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1261908|要取消之前显示的Toast并立即显示新的Toast，最好的方法是保留对当前显示的one的引用，以便能够取消它。所以使用这些扩展函数真的很有帮助：|1261909|​|1261910|ToastUtils.kt|1261911|import+android.content.Context
import+android.widget.Toast
import+androidx.annotation.StringRes

/**
+*+@author+aminography
+*/

private+var+toast:+Toast?+=+null

fun+Context.toast(message:+CharSequence?)+{
++++toast?.cancel()
++++toast+=+message?.let+{+Toast.makeText(this,+it,+Toast.LENGTH_SHORT)+}?.apply+{+show()+}
}

fun+Context.longToast(message:+CharSequence?)+{
++++toast?.cancel()
++++toast+=+message?.let+{+Toast.makeText(this,+it,+Toast.LENGTH_LONG)+}?.apply+{+show()+}
}

fun+Context.toast(@StringRes+message:+Int)+{
++++toast?.cancel()
++++toast+=+Toast.makeText(this,+message,+Toast.LENGTH_SHORT).apply+{+show()+}
}

fun+Context.longToast(@StringRes+message:+Int)+{
++++toast?.cancel()
++++toast+=+Toast.makeText(this,+message,+Toast.LENGTH_LONG).apply+{+show()+}
}|code-block|syntax|javascript|1261912|1261913|用法：|1261914|context.toast("Text+1")
context.longToast("Text+2")

context.toast(R.string.text3)
context.longToast(R.string.text4)|1261915|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/aminography/CommonUtils/blob/master/library/src/main/java/com/aminography/commonutils/ToastUtils.kt^0|3|I|N|E|0|8|5|K|5|0|0|0|D|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1D|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|L|3|M|5|N|7|1I|8|@]|D|@]|E|$O|P]]|$1|Q|3|I|5|6|7|1J|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1K|8|@]|D|@]|E|$]]|$1|T|3|U|5|N|7|1L|8|@]|D|@]|E|$O|P]]|$1|V|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]]]

<h2>• <code>Kotlin Version</code> via <code>Extension Function</code></h2>
The best way to cancel previously shown <code>Toast</code> and display a new one instantly is to keep a reference to the currently shown <code>Toast</code> to be able to cancel it. So using these extension functions really helps:
 
<h3><a href="https://github.com/aminography/CommonUtils/blob/master/library/src/main/java/com/aminography/commonutils/ToastUtils.kt" rel="nofollow noreferrer">ToastUtils.kt</a></h3>
<pre><code>import android.content.Context
import android.widget.Toast
import androidx.annotation.StringRes

/**
 * @author aminography
 */

private var toast: Toast? = null

fun Context.toast(message: CharSequence?) {
 toast?.cancel()
 toast = message?.let { Toast.makeText(this, it, Toast.LENGTH_SHORT) }?.apply { show() }
}

fun Context.longToast(message: CharSequence?) {
 toast?.cancel()
 toast = message?.let { Toast.makeText(this, it, Toast.LENGTH_LONG) }?.apply { show() }
}

fun Context.toast(@StringRes message: Int) {
 toast?.cancel()
 toast = Toast.makeText(this, message, Toast.LENGTH_SHORT).apply { show() }
}

fun Context.longToast(@StringRes message: Int) {
 toast?.cancel()
 toast = Toast.makeText(this, message, Toast.LENGTH_LONG).apply { show() }
}
</code></pre>
 
<h3>Usage:</h3>
<pre><code>context.toast(&quot;Text 1&quot;)
context.longToast(&quot;Text 2&quot;)

context.toast(R.string.text3)
context.longToast(R.string.text4)
</code></pre>

blocks|key|1261391|text|我就是这么做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261392|Toast+toast;+++

if(toast==null)
++++++++toast=Toast.makeText(getApplicationContext(),R.string.act_now_private_post_text,Toast.LENGTH_LONG);
++++++++else
++++++++++++toast.setText(R.string.act_now_private_post_text);
++++++++toast.setGravity(Gravity.CENTER_VERTICAL%7CGravity.CENTER_HORIZONTAL,10,10);
++++++++toast.show();|code-block|syntax|javascript|1261393|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is how I do it.

<pre><code>Toast toast; 

if(toast==null)
 toast=Toast.makeText(getApplicationContext(),R.string.act_now_private_post_text,Toast.LENGTH_LONG);
 else
 toast.setText(R.string.act_now_private_post_text);
 toast.setGravity(Gravity.CENTER_VERTICAL|Gravity.CENTER_HORIZONTAL,10,10);
 toast.show();
</code></pre>

blocks|key|1261237|text|mToast=Toast.makeText(this,+"",+Toast.LENGTH_LONG);
++++++++showToast.setOnClickListener(new+OnClickListener()+{
++++++++++++public+void+onClick(View+v)+{

++++++++++++++++mToast.cancel();
++++++++++++++++String+text=null;
++++++++++++++++if(ON)
++++++++++++++++{
++++++++++++++++++++text="Toast+is+on";
++++++++++++++++}
++++++++++++++++else
++++++++++++++++{
++++++++++++++++++++text="Toast+is+off";
++++++++++++++++}
++++++++++++++++mToast.setText(text);
++++++++++++++++mToast.setDuration(Toast.LENGTH_SHORT);
++++++++++++++++mToast.show();

++++++++++++}
++++++++});|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1261238|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>mToast=Toast.makeText(this, "", Toast.LENGTH_LONG);
 showToast.setOnClickListener(new OnClickListener() {
 public void onClick(View v) {

 mToast.cancel();
 String text=null;
 if(ON)
 {
 text="Toast is on";
 }
 else
 {
 text="Toast is off";
 }
 mToast.setText(text);
 mToast.setDuration(Toast.LENGTH_SHORT);
 mToast.show();

 }
 });
</code></pre>

blocks|key|1046580|text|你可以像这样使用..|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1046581|class+MyToast+{
private+static+Toast+t;

public+MyToast(Context+ctx,+String+message)+{
++++if+(t+!=+null)+{
++++++++t.cancel();
++++++++t+=+null;
++++}
++++t+=+Toast.makeText(ctx,+message,+Toast.LENGTH_SHORT);
}

public+void+show()+{
++++t.show();
}
}|code-block|syntax|javascript|1046582|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can use like this..

<pre><code>class MyToast {
private static Toast t;

public MyToast(Context ctx, String message) {
 if (t != null) {
 t.cancel();
 t = null;
 }
 t = Toast.makeText(ctx, message, Toast.LENGTH_SHORT);
}

public void show() {
 t.show();
}
}
</code></pre>

blocks|key|1261520|text|使用上面Madur的出色答案，我将其扩展为一个处理不同类型消息的类：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261521|public+class+ToastManager+{
++++private+Toast+toastWarningMessage;
++++private+Toast+toastAddMessage;
++++...

++++public+void+messageWarning(Context+context,+String+message)+{
++++++++if(toastWarningMessage+==+null)+{
++++++++++++toastWarningMessage+=+Toast.makeText(context,+message,+Toast.LENGTH_SHORT);
++++++++}+else+{
++++++++++++toastWarningMessage.cancel();
++++++++++++toastWarningMessage.setText(message);
++++++++}
++++++++toastWarningMessage.show();
++++}

++++public+void+messageAdd(Context+context,+String+message)+{
++++++++if(toastAddMessage+==+null)+{
++++++++++++toastAddMessage+=+Toast.makeText(context,+message,+Toast.LENGTH_SHORT);
++++++++}+else+{
++++++++++++toastAddMessage.cancel();
++++++++++++toastAddMessage.setText(message);
++++++++}
++++++++toastAddMessage.show();
++++}
++++...
}|code-block|syntax|javascript|1261522|这是在我的主活动中调用的：|1261523|ToastManager+toastManager;
...
private+void+toastWarningMessage(String+message)+{
++++if(toastManager+==+null)+toastManager+=+new+ToastManager();
++++toastManager.messageWarning(this,+message);
}|1261524|对消息进行分类的原因是为了确保重要消息不会被覆盖。这个解决方案似乎很容易重用，因为它只涉及到重命名Toast和函数名称。|1261525|当用户按下垃圾邮件按钮时，每次都会取消相同类型的消息。唯一的问题是，如果用户可以垃圾邮件的混合。这导致第一条消息重复，一旦它最终过期，其他消息各显示一次。这并不是一个大问题，但需要注意的是。|1261526|我还没有研究过拥有多个Toast实例的可能的缺点。|1261527|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Using Madur's excellent answer above, I extended this into a class that would deal with different types of messages:

<pre><code>public class ToastManager {
 private Toast toastWarningMessage;
 private Toast toastAddMessage;
 ...

 public void messageWarning(Context context, String message) {
 if(toastWarningMessage == null) {
 toastWarningMessage = Toast.makeText(context, message, Toast.LENGTH_SHORT);
 } else {
 toastWarningMessage.cancel();
 toastWarningMessage.setText(message);
 }
 toastWarningMessage.show();
 }

 public void messageAdd(Context context, String message) {
 if(toastAddMessage == null) {
 toastAddMessage = Toast.makeText(context, message, Toast.LENGTH_SHORT);
 } else {
 toastAddMessage.cancel();
 toastAddMessage.setText(message);
 }
 toastAddMessage.show();
 }
 ...
}
</code></pre>

And this is called from within my main activity:

<pre><code>ToastManager toastManager;
...
private void toastWarningMessage(String message) {
 if(toastManager == null) toastManager = new ToastManager();
 toastManager.messageWarning(this, message);
}
</code></pre>

The reason for classifying the messages is to make sure that no important messages are overwritten. This solution seems easy to reuse as it only involves renaming the Toasts and the function names. 

When the user spams the button, the toast will just cancel each time for the same message type. The only problem is if the user can spam a mix of messages. This leads to the first message repeating and once it finally expires the other messages showing once each. Not really a huge problem, but something to be aware of.

I haven't looked into possible downsides of having multiple Toast instances.

blocks|key|1261693|text|在我的应用程序中，当应用程序进入后台时，排队的吐司一次又一次地出现，所以我做了以下操作来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261694|添加代码以检测应用程序何时进入后台。注册生命周期处理程序的一种方法。有关详细信息，请参阅ref|offset|length|1261695|registerActivityLifecycleCallbacks(new+MyLifecycleHandler());|code-block|syntax|javascript|1261696|当应用程序转到后台并使用SmartToast类显示吐司时使用App.inBackground+=+true;|style|CODE|1261697|public+class+SmartToast+{

++++static+ArrayList<WeakReference<Toast>>+toasts+=+new+ArrayList<>();
++++public+static+void+showToast(@NonNull+Context+context,@NonNull+String+message){
++++++++//this+will+not+allowed+to+show+toast+when+app+in+background
++++++++if(App.inBackground)+return;
++++++++Toast+toast+=+Toast.makeText(context,message,Toast.LENGTH_SHORT);
++++++++toasts.add(new+WeakReference<>(toast));
++++++++toast.show();

++++++++//clean+up+WeakReference+objects+itself
++++++++ArrayList<WeakReference<Toast>>+nullToasts+=+new+ArrayList<>();
++++++++for+(WeakReference<Toast>+weakToast+:+toasts)+{
++++++++++++if(weakToast.get()+==+null)+nullToasts.add(weakToast);
++++++++}
++++++++toasts.remove(nullToasts);
++++}

++++public+static+void+cancelAll(){
++++++++for+(WeakReference<Toast>+weakToast+:+toasts)+{
++++++++++++if(weakToast.get()+!=+null)+weakToast.get().cancel();
++++++++}
++++++++toasts.clear();
++++}

}|1261698|当app进入后台时，调用SmartToast.cancelAll();方法隐藏当前和所有挂起的吐司。代码很有趣。享受吧！|1261699|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4414171/how-to-detect-when-an-android-app-goes-to-the-background-and-come-back-to-the-fo^0|0|18|3|0|0|0|U|O|0|0|C|N|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|16|8|@$D|17|E|18|M|N]]|9|@]|A|$]]|$1|O|3|P|5|H|7|19|8|@]|9|@]|A|$I|J]]|$1|Q|3|R|5|6|7|1A|8|@$D|1B|E|1C|M|N]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

In my app, queued toasts appearing again and again when app goes into background so I did following to solve the problem.

Add code to detect when app goes into background. One way to register life cycle handler. For More detail <a href="https://stackoverflow.com/questions/4414171/how-to-detect-when-an-android-app-goes-to-the-background-and-come-back-to-the-fo">ref</a>

<pre><code>registerActivityLifecycleCallbacks(new MyLifecycleHandler());
</code></pre>

<code>App.inBackground = true;</code> when app goes to background and show toast using SmartToast class

<pre><code>public class SmartToast {

 static ArrayList&lt;WeakReference&lt;Toast&gt;&gt; toasts = new ArrayList&lt;&gt;();
 public static void showToast(@NonNull Context context,@NonNull String message){
 //this will not allowed to show toast when app in background
 if(App.inBackground) return;
 Toast toast = Toast.makeText(context,message,Toast.LENGTH_SHORT);
 toasts.add(new WeakReference&lt;&gt;(toast));
 toast.show();

 //clean up WeakReference objects itself
 ArrayList&lt;WeakReference&lt;Toast&gt;&gt; nullToasts = new ArrayList&lt;&gt;();
 for (WeakReference&lt;Toast&gt; weakToast : toasts) {
 if(weakToast.get() == null) nullToasts.add(weakToast);
 }
 toasts.remove(nullToasts);
 }

 public static void cancelAll(){
 for (WeakReference&lt;Toast&gt; weakToast : toasts) {
 if(weakToast.get() != null) weakToast.get().cancel();
 }
 toasts.clear();
 }

}
</code></pre>

call <code>SmartToast.cancelAll();</code> method when app goes into background to hide current and all pending toasts. Code is fun. Enjoy!

blocks|key|1261855|text|这些怎么样!？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261856|private+Toast+toast;

...
//+Methods+for+short+toast+messages+and+long+toast+messages

++++private+void+showShortToast(String+message)+{
++++++++if(null+!=+toast)+toast.cancel();
++++++++(toast+=+Toast.makeText(getApplicationContext(),+message,+Toast.LENGTH_SHORT)).show();
++++}

++++private+void+showLongToast(String+message)+{
++++++++if(null+!=+toast)+toast.cancel();
++++++++(toast+=+Toast.makeText(getApplicationContext(),+message,+Toast.LENGTH_LONG)).show();
++++}|code-block|syntax|javascript|1261857|和onPause()|1261858|@Override
++++protected+void+onPause()+{
...
if(null+!=+toast)+toast.cancel();
..
}|1261859|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

How about these !?

<pre><code>private Toast toast;

...
// Methods for short toast messages and long toast messages

 private void showShortToast(String message) {
 if(null != toast) toast.cancel();
 (toast = Toast.makeText(getApplicationContext(), message, Toast.LENGTH_SHORT)).show();
 }

 private void showLongToast(String message) {
 if(null != toast) toast.cancel();
 (toast = Toast.makeText(getApplicationContext(), message, Toast.LENGTH_LONG)).show();
 }
</code></pre>

and at onPause()

<pre><code>@Override
 protected void onPause() {
...
if(null != toast) toast.cancel();
..
}
</code></pre>

blocks|key|1046453|text|下面是如何禁用toast消息，删除show()表达式。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1046454|//Disable+notification+message
Toast.makeText(this,"Message",Toast.LENGTH_SHORT);+

//Enable+notification+message
Toast.makeText(this,"Message",Toast.LENGTH_SHORT).show();|code-block|syntax|javascript|1046455|entityMap^0|H|6|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Here's how to disable toast messages, remove <code>show()</code> expression.

<pre><code>//Disable notification message
Toast.makeText(this,"Message",Toast.LENGTH_SHORT); 

//Enable notification message
Toast.makeText(this,"Message",Toast.LENGTH_SHORT).show();
</code></pre>

How do I remove all toast messages currently displayed?

In my App, there is a list, when a user clicks on an item, a toast message is displayed,
10 items - 10 toast messages.

So if the user clicks 10 times, then presses the menu button, they have to wait for some seconds until they're able to read the menu option text.

It shouldn't be like that :)

Android - Hide all shown Toast Messages

Kotlin

如何删除当前显示的所有toast消息？在我的应用中，有一个列表，当用户点击一个项目时，会显示一条吐司消息，10个项目- 10个吐司消息。因此，如果用户点击10次，然后按下菜单按钮，他们必须等待几秒钟，直到他们能够阅读菜单选项文本。它不应该是这样的:)

问Android -隐藏所有显示的Toast消息
EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android -隐藏所有显示的Toast消息EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android -隐藏所有显示的Toast消息
EN