LucaMs Expert Licensed User Longtime User Dec 5, 2017 #1 I understand how to use the version 2 of MsgBoxAsync with Wait For: Code: Copy Msgbox2Async("Message", "Title", "Positive", "Cancel", "Negative", Bmp, False) Wait For MsgBox_Result (Result As Int) If Result = DialogResponse.NEGATIVE Then but not how to use the simple MsgBoxAsync; this does not work: Code: Copy Wait For MsgboxAsync("Message", "Title")
I understand how to use the version 2 of MsgBoxAsync with Wait For: Code: Copy Msgbox2Async("Message", "Title", "Positive", "Cancel", "Negative", Bmp, False) Wait For MsgBox_Result (Result As Int) If Result = DialogResponse.NEGATIVE Then but not how to use the simple MsgBoxAsync; this does not work: Code: Copy Wait For MsgboxAsync("Message", "Title")
LucaMs Expert Licensed User Longtime User Dec 5, 2017 #2 Answer: same way: Code: Copy MsgboxAsync("Message", "Title") Wait For MsgBox_Result (Result As Int) The contextual help has deceived me, it seems that the "version 1" does not return a value: Upvote 0
Answer: same way: Code: Copy MsgboxAsync("Message", "Title") Wait For MsgBox_Result (Result As Int) The contextual help has deceived me, it seems that the "version 1" does not return a value:
DonManfred Expert Licensed User Longtime User Dec 5, 2017 #3 Code: Copy MsgboxAsync("Message", "Title") Wait For MsgBox_Result (Result As Int) If Result = DialogResponse.POSITIVE Then Upvote 0
Code: Copy MsgboxAsync("Message", "Title") Wait For MsgBox_Result (Result As Int) If Result = DialogResponse.POSITIVE Then
Erel B4X founder Staff member Licensed User Longtime User Dec 5, 2017 #4 BTW, in most cases there is no reason to wait for the user to close it. Just show it and continue. It is not the same as Msgbox2Async where you are waiting for the user choice. Upvote 0
BTW, in most cases there is no reason to wait for the user to close it. Just show it and continue. It is not the same as Msgbox2Async where you are waiting for the user choice.
LucaMs Expert Licensed User Longtime User Dec 5, 2017 #5 Erel said: BTW, in most cases there is no reason to wait for the user to close it. Just show it and continue. It is not the same as Msgbox2Async where you are waiting for the user choice. Click to expand... Yes, but in my case I have to inform the user that he must update the app and then close it. Thank you Upvote 0
Erel said: BTW, in most cases there is no reason to wait for the user to close it. Just show it and continue. It is not the same as Msgbox2Async where you are waiting for the user choice. Click to expand... Yes, but in my case I have to inform the user that he must update the app and then close it. Thank you
