* add basic reaction view
* reuse pill background
* make pill border a little more visible; this affects sended reactions as well as received ones
* use 🤣 instead of 😂 to differ more from 😢
also, 😂 is a bit outdated for younger generations
(so is probably 🤣 but not that much)
(alternative would be 💀 for laughing,
but that is probably not compatible between generations)
* use 🙁 instead of 😢 for 'sad' to distict from lol
lol gets revered to 😂 as
🤣 seems to be even a more non-go (thanks for expertise, young folks!)
* wording: we add one reaction, not many
* show/hide add-reaction-view together with action mode
* pass message&view to showAddReactionView()
* add sendReactions() api
* create AddReactionView class
* send reactions on click
* hide AddReactiobView on sending emoji
* detect self-reaction
* feat: remove selections
* position AddReactionView atop of parent view
* move AddReactionView up a bit
* padding top/bottom
* center for now, this also postpones rtl/ltr
* force initial layout
* move slightly more off the bubble, keep away a bit from screen margin
* move AddReactionsView left/right depending on incoming/outgoing mails
* do not allow reactions in read-only chats
* do not allow to react to videochat-invitations and info; the latter may makes sense at some point, however, to lower burder on other implementations, we do not send them for now
* hide reaction-picker when leaving action mode with 'back'
* hide reaction-picker when leaving action mode with 'back'
* scroll reaction-panel together with recyclerview; this does not happen if new messages come in, however, this is a minor (and a stable panel position can be regarded even as a feature)
* add sending reactions as an experimental feature as long not at least all system display reactions
* clarify that reactions are currently not seen by all members
* prefer View.INVISIBLE over offscreen hack
See deltachat/deltachat-core-rust#2514
Fixes#1963Fixes#1890
Before deleting a chat the user is asked for confirmation. Before blocking not, because blocking is not "destructive" (i.e. can be completely reverted by unblocking the contact). I'm wondering whether we should show a snackbar with an Undo button though, but we can probably wait for user feedback on this.
* Start removing deaddrop chat
* Generally works
* Fix the buttons
(it's not easy to not show one of the buttons in
ConstraintLayout; if problems turn up, we should probably
just not use ConstraintLayout)
* fix more things
* restartLoader() instead of notifyDataSetChanged() because the latter didn't do anything
* Archived badge
* Rename "Contact request" to "Request"
* oops
* Remove setStockTranslation(8, context.getString(R.string.chat_contact_request));
* Remove commented-out code, we probably won't need it
* Don't show "Delete" button for 1:1 chats
* Get rid of short flickering when declining a request
* Set the app's night mode to match the preference
This added 6ms to startup time, but I think that's OK, as
we will also be able to use more `-night` views in the future
* Make "Accept" text a bit brighter and easier to read in dark mode
* Check if the chattype is Group instead of members.length == 1
bjoern