Develop Reference

How to dismiss a MaterialAlertDialog when a hyperlink is clicked?

Is there a way to dismiss/cancel a MaterialAlertDialog when a hyperlink inside the message was clicked?
Currently the browser is open and when you returned to the app the dialog is still open.
For the buttons there is a listener where you can dismiss/cancel the dialog.
What I want to achieve is to close the dialog when the link is clicked.

add onClickListener to TextView containing hyperlink
use onResume() method to close dialog after you return to it

After reading a bit about setLinkMovementMethod I thought about somethink like:
textView.setLinkMovementMethod(new TextViewLinkHandler() {
// do my stuff ...
// if left blank, nothing will happen on click at the link, so leave it blank to do nothing
})
With the mentioned TextViewLinkHandler()
public abstract class TextViewLinkHandler extends LinkMovementMethod {
// add a method to handle the click
// extract the url and open it
// then dismiss the dialog
}
But maybe this is not the right approach.
What did you think?

Build dialog one after one in a loop

I have this function where I need to return a list depending of what user pressed in Alert Dialog (cancel or save).
But I have an issue, let's imagine we have a list with a size of 10. Then on the iteration of that list it will build 10 alert dialogs at the same time plus a dark black shadow at the background caused by these.
So I'd like to "pause" until user pressed or find a way to don't pop up all these alert dialog at the same time and just appear one by one once pressed a button.
A quick reminder: I need to return a list after all dialogs have been pressed.
Question: How could I do that?

It would be better if you provided some code with this. Anyway, even though this is not something I would do and create 10 dialogs in the for loop, this can be done.
Just create a Boolean inside your for loop which will be used to check if the dialog is dismissed.
for(int i = 0; i < list.size(); ++i) {
Boolean isDismissed = false;
AlertDialog d = new AlertDialog(getBaseContext());
d.setOnDismissListener(new DialogInterface.OnDismissListener() {
#Override
public void onDismiss(DialogInterface dialog) {
isDismissed = true;
}
});
//start your dialog
while(!isDismissed) {
//do nothing
}
}
As I said, I wouldn't do this.
Because I evaluate first a list of items, then I set on a new list of items that will require user to confirm about what to do with that, so I loop that with alert dialogs waiting for user to tell me what to do with those items
There is a much better way to do this. Why not starting one CustomDialog which will ask the user what to do with those items. He could choose options for each item with a spinner or if options are KEEP or DELETE just use checkbox or something.

So as people said, creating Alert Dialogs in a loop is a bad practice so my solution into this is just setting a view on Fragment that acts like a Dialog but I just turn it visible and gone whenever I need. This seems a proper solution for my case.
When user accept or cancel the view (clicking on button) just send it to the viewmodel and the viewmodel will evaluate if there are still items on the list. If there are items then show again this "view" on Fragment asking to user what to do :)
I don't have code to show because I haven't done it yet but I have thought for a while and this is the best I can think about. Hope it helps for someone who is in the same situation!

Make Button in Android to repeat process inside activity until counter reaches certain number

I currently have Button in my main view which checks if users answer is correct.
Button CheckButton= (Button) this.findViewById(R.id.CheckButton);
CheckButton.setOnClickListener(new OnClickListener()
{
public void onClick(View v) {
// some action, setting text
}
});
If button is pressed once it checks if answer is correct, and if button is pressed second time I want it to repeat activity e.g. present user with another question.
OnClickListener is inside onCreate method and question is generated using switch and unique id (for game difficulty).
What would be the best way to set this repeat activity until it's been repeated 4 times. Thanks
switch (difficulty_level)
{
case DIFFICULTY_HARD:
// do this
case DIFFICULTY_EASY:
// do this
}

To me, this doesn't sound like logic belonging in the OnClickListener at all. The listener should simply register the click and then call a function in your activity "handleButtonClicked" that have access to fields that keep track of the number of clicks for the question, if the answer is correct and what the appropiate action is.
The fact that the OnClickListener is set in the onCreate only says that it is ready to be used after OnCreate. It doesn't require the OnCreate to be run again.

Instead of an anonymous inner implementation of OnClickListener, define it as a private class.
That way you can pass the parameter of how many iterations you want in its constructor / setter
Each time the application is launched, increase a counter; when such counter is bigger or equal than the said parameters, ignore the following clicks

You need a global state variable that you set when the click has occured twice, or you could just count and every even number you change the question by loading another activity.

How to simulate a button click using code?

How can I trigger a button click event using code in Android? I want to trigger the button click programmatically when some other event occurs.
Same Problem I am Facing
public void onDateSelectedButtonClick(View v){
/*Something Alarm Management
http://www.java2s.com/Code/Android/Core-Class/Alarmdemo.htm
copied code from this site*/
}
Button code:
<Button
android:onClick="onDateSelectedButtonClick"
android:text="Set notification for this date" />
But I want to call that function OnLoadLayout without OnClickEvent

there is a better way.
View.performClick();
http://developer.android.com/reference/android/view/View.html#performClick()
this should answer all your problems. every View inherits this function, including Button, Spinner, etc.
Just to clarify, View does not have a static performClick() method. You must call performClick() on an instance of View.
For example, you can't just call
View.performClick();
Instead, do something like:
View myView = findViewById(R.id.myview);
myView.performClick();

Just to clarify what moonlightcheese stated:
To trigger a button click event through code in Android
provide the following:
buttonName.performClick();

you can do it this way
private Button btn;
btn = (Button)findViewById(R.id.button2);
btn.performClick();

Just write this simple line of code :-
button.performClick();
where button is the reference variable of Button class and defined as follows:-
private Button buttonToday ;
buttonToday = (Button) findViewById(R.id.buttonToday);
That's it.

Android's callOnClick() (added in API 15) can sometimes be a better choice in my experience than performClick(). If a user has selection sounds enabled, then performClick() could cause the user to hear two continuous selection sounds that are somewhat layered on top of each other which can be jarring. (One selection sound for the user's first button click, and then another for the other button's OnClickListener that you're calling via code.)

Starting with API15, you can use also callOnClick() that directly call attached view OnClickListener. Unlike performClick(), this only calls the listener, and does not do any associated clicking actions like reporting an accessibility event.

If you do not use the sender argument, why not refactor the button handler implementation to separate function, and call it from wherever you want (from the button handler and from the other place).
Anyway, it is a better and cleaner design - a code that needs to be called on button handler AND from some other places deserves to be refactored to own function. Plus it will help you separate UI handling from application logic code. You will also have a nice name to the function, not just onDateSelectedButtonClick().

Android Class which extends Dialog, how to clear TextViews before it is displayed

I have a class that extends android.app.Dialog, the layout is done in an xml file, and the setup (button listeners, etc) is done on the onCreate method. My problem is that whenever the dialog is displayed, then dismissed, and displayed again, the Editable TextViews are still populated with the information that was displayed previously. What is the common way to clear these text fields? Remember - this is a separate class that extends Dialog - so there is no 'onDialogCreate' like Activity has.
Or, perhaps I am extending the wrong class? There is just a lot of processing being done, and do not want to have all the code in the main Activity. I would like it to be in a separate Class. I tried to extend AlertDialog, but it does not create the border like Dialog does. Any help would be great.
The dialog is shown via the Activity:
protected Dialog onCreateDialog(int id) {
switch(id){
case DIALOG_NEW_SAFE:
return(new NewSafeDialog(this));
default:
return(null);
}
}

onCreateDialog(..) caches the dialog which means the same instance is reused.
3 ways to fix the undesired behavior off my head:
Override onPrepareDialog(..), use findViewById(..) to get whatever you want to clear, clear it.
Don't rely on managed dialogs at all, do new NewSafeDialog(this).show() each time you want to show the dialog.
Add onCancelListener(..), onDismissListener(..) inside your custom dialog that would call a method to clear itself.

The good way to create a dialog is by using showDialog() as you did so don't change it.
The good and easy way to force deletion of a dialog in order to make your creation code recalled again is:
void removeDialog (int id)
So if you simply do the following, it's gonna work ;)
removeDialog(DIALOG_NEW_SAFE);
showDialog(DIALOG_NEW_SAFE);

Try clearing the text in the constructor of the NewSafeDialog i.e. your dialog class.