The last thing we need to is add a menu.

An easy way to do this,

is to copy the code from a project that already has a menu.

Luckily, Android studio creates lots of those.

Let's pick this one, with the three dots in the corner.

We'll want this menumain.xml file for ourselves.

We don't even have a menu folder under our res directory yet.

So I'll just copy the whole directory.

This is the string that will display when we click the menu button.

So let's hit Alt+Enter to create this.

We want it to say clear strokes.

It would also be nice if it had a more descriptive name.

We can go to re-factor, rename, noting that the keyboard shortcut is shift F6,

and then name it action clear strokes.

And we'll do the same thing for the ID.

Except this time we'll use the Shift+F6 shortcut.

All right.

Now we need to add the code and main activity to use that menu.

We can grab that code from the project we just generated as well.

And main activity.

Below onCreate we'll want the onCreateMenuOptions and

onOptionsItemSelected file methods.

And we'll paste them below on pause.

Recall that we changed our action settings to be action clear strokes.

And now we can add the code that we'd like to execute when that button is pressed.

What we'd like to happen is for each of the holes to reset their stroke count

to zero, as well as to not to have any saved data with those strokes either.

So we'll take our editor.

And we'll hit clear to remove all the shared preference values,

and then mEditor.apply to save our changes.

After that, we need to set each of the whole scores to zero.

Instead of using a for loop, using int I equals zero, like I have been doing.

This time I'll use a for each loop to show something different.

So four, we're going to be using holes.

And we're going to call the holes in the loop hole, from the group called m holes.

And for each hole, we wanna set the stroke count to zero.

Okay.

That should do it.

Let's see what happens.

Well, right off the bat, it's pretty clear that we don't have a bar up here.

And we'd like one.

Let's hop over to Google and see what that's all about.

I Googled for list activity, no action bar.

And on the second result,

We learn that only themes after Holo can get action bars.

And our theme, let's double check it against this first,

is AppCompat.Light.DarkActionBar.

Which is exactly what he says might cause us trouble.

So let's try changing it to

Android:Theme.Holo.

All right.

We've got our action bar.

And we've got an awfully dark theme, if you like this theme that's great,

if you don't we can change this to Holo.Light.

Looks good.

So what happens when we clear the strokes?

Nothing, nothing happened.

Three, two, one, zeros, zeros.

What's going on here is when we clear the strokes,

we're clearing them in the data and the data is correct.

But what's being shown to us is not being updated.

We haven't told the list view to update.

By scrolling up and down, we can make it update each of the views, and so

if we clear the strokes and scroll down, and then come back up, it'll be zero.

But it won't be 0 right when we hit Clear Strokes because we haven't added any code

to clear that yet.

This is an easy fix though.

In MainActivity.java, right after we set all the hole stroke counts to 0

All we need to do is call notifyDataSetChanged on our list adaptor.

So, mlistadaptor.notifyDataSetChanged.

And this tells the list adaptor that the data set changed.

And the list adaptor knows that when that happens it needs to update.

So that should handle that bug.

Let's run it and find out.

All right, lets add some scores and then clear them.

Looks good.

And if we leave, and then come back, still zeros.

Let's test a rotation just for good measure.

Looks good. And it looks like we're done with the app.

Great job.

If you're looking for

more things to add to this app, a good place to start would be the app icon.

Congratulations on finishing the Golf Scorecard app.

It was definitely a lot of work.

But being able to put all the pieces together and

create a finished product, is definitely worth it.

You’re now well on your way to becoming an Android developer, and

I look forward to seeing what you choose to make next.