Add action indicator when resending a message.

[greenjoe]

First time contributor checklist

• I have read how to contribute to this project
• I have signed the Contributor License Agreement

Contributor checklist

• I am following the Code Style Guidelines
• I have tested my contribution on these devices:

• Nexus 5x, Android 7.1.1

• My contribution is fully baked and ready to be merged as is
• I ensure that all the open issues my contribution fixes are mentioned in the commit message of my first commit using the Fixes #1234 syntax
• I have made the choice whether I want the BitHub reward or not by omitting or adding the word FREEBIE in the commit message of my first commit

---

Description

When sending of message fails, user can go into details of that message and click RESEND button to retry. As issue #6307 mentions, after clicking that button nothing really indicates on the screen that message is being resent in the background.

This pull request hides the RESEND button when resending asynchronous task is started, as well as hides the "error_description" TextView and replaces it with the "action_description" TextView which says "Resending...". That should provide a nice indicator that clicking the RESEND button actually had an effect.

[mammuth]

Cool! 👍
What happens if the sending fails another time? Becomes the resend-button visible again and the indicator (actionDescription) is removed?

[greenjoe]

@mammuth Thanks, I've tested the case when sending fails multiple times as well as the case when it fails and then succeeds and it seems to work fine.

There is no explicit code to make the resend-button visible again and hide the actionDescription, but I believe that every time resending is finished the whole MessageRecipientListItem view is created again from scratch. Behavior that is now present in the master branch, which is to just make RESEND button disabled, also probably relies on the fact that the view will be created again (there is no code to re-enable the button).

I'm not an android developer by trade so I'm not 100% sure that my understanding is correct, but it looks like

• MessageDetailsActivity creates instance of MessageDetailsLoader that loads message details
• MessageDetailsActivity.onLoadFinished is called every time the resending task finishes and executes MessageRecipientAsyncTask
• That task calls MessageDetailsActivity.updateRecipients which creates a new adapter recipientsList.setAdapter(new MessageDetailsRecipientAdapter(...)); and the adapter in turn creates new instances of MessageRecipientListItem class.

Please correct me if I'm wrong :-)

[McLoo]

IRRC we moved to ... instad of using … (just 3 string left)

[greenjoe]

Well Android Studio suggested using the entity instead of three dots and I checked if the entity is used anywhere in the file - it was, so I used it too. Now I see that there are indeed more usages of three dots than of the entity. I can change it if it is important, but I believe it may be better to just do find and replace in one commit and change all the instances instead.

[moxie0]

Did you try changing the button label and seeing how that looks instead of adding a new view that you swap?

[greenjoe]

@moxie0
I believe that it looks better when using textview, especially when translation of "Resending" is long. I also think that there's no point displaying a button when it cannot be clicked and I believe it's nice if that red text disappears when you already took an action.

The screenshots from both options are below so you can judge it yourself (I'm sorry they are "reddish", I forgot to turn Twilight off).
The changes for the "simpler" version are here greenjoe@12b19bf and I can create a pull request with them if you like it more.

Textview (as in this pull request):

Button label:

And when translations are longer (used polish strings, I was too lazy to change language of the whole app)

Textview:

Button label: