Add two reaction UX improvements on top of the send-reaction feature:
- Double-tap a message bubble to send the configured default reaction
emoji. A single GestureDetector on the item root now handles tap,
double-tap and long-press, leaving child view touch handling intact.
- Configurable per-direction message swipe actions (none, react, reply,
copy, forward, delete) via a new MessageItemTouchCallback that always
snaps the row back after a swipe. Adds a settings screen for the swipe
actions and a default-reaction emoji picker, backed by new preferences.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Address review findings on the send-reaction feature:
- Run permission checks on the main thread and only switch to IO for the
actual send, instead of touching the UI from a background thread.
- Parse outgoing reactions on the sender's own device. Sent messages don't
arrive back as incoming, so they would otherwise never be attached or
hidden until a full reparse.
- Anchor the reaction picker above the long-pressed message instead of
centering it on the screen, falling back to the list when off-screen.
- Always send reactions as group MMS in a group thread.
- Attribute our own reactions to our own number (via isMe + getMyPhoneNumber)
rather than the recipient's address, and show "Me" for them in the
reactions dialog.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Long-press a message to open an emoji reaction picker. Reactions are
sent as a plain SMS/MMS body using a quik-specific zero-width encoding
that carries the original sender's address and the message's timestamp,
so a receiving quik instance can attach the reaction to the exact
message via address + date lookup (fast path), falling back to the
existing text matching for non-quik senders.
The quik pattern is registered first so it wins over the generic Google
Messages pattern; iOS/Google parsing is unchanged. New ParsedEmojiReaction
fields are in-memory only, so no Realm migration is needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The previous behavior fetched scheduled messages directly from the conversation adaptor. This was causing memory leaks and potentially crashes. Now, the view model fetches it and provides the data through state.
The app was setting gallery to black mode programmatically, and for some reason this was affecting other activities theming. We can just use a custom theme to force black mode that won't mess with other screens.
For some asinine reason, `state.scheduled` was observed than set with the same value, which was causing an infinite loop. `scheduled` is completely irrelevant to `canSend` anyway, as scheduled is essentially a boolean, and it is handled elsewhere.
Store ViewBinding in the ViewHolder instead of recreating it via
.bind() on every onBindViewHolder call. This reduces allocations
and simplifies the code.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add widget and checkbox properties to PreferenceView, eliminating
repetitive findViewById<QkSwitch>(R.id.checkbox) calls throughout
the codebase.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Adds a new class of features for message management.
- Adds a manual option to find and delete duplicate messages
- Adds a setting to automatically delete duplicates during sync
- Adds a sha256 hashing function
Co-authored-by: octoshrimpy <octoshrimpy@users.noreply.github.com>
The switchMap was causing a crash because it was trying to use conversation as an observable, even though it is not. (caused by c3df5f231f) There is no need for this code, because the whole function is now an observable.