UnigramDev/Unigram/develop • b5bf963 • 1 files, +3/-0 Assign the flag SearchResult is constructed wi

UnigramDev/Unigram/develop • b5bf963 • 1 files, +3/-0
Assign the flag SearchResult is constructed with

Every constructor took canSendMessageToUser and dropped it, so the field was
always false and the restricts-new-chats indicator could never appear.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

UnigramDev/Unigram/develop • 004ff43 • 14 files, +3/-20
Code cleanup

UnigramDev/Unigram/develop • 3060ffb • 1 files, +2/-2
Fix live location style registration

UnigramDev/Unigram/develop • 2a4fbd3 • 1 files, +7/-3
Access violation guard

UnigramDev/Unigram/develop • bbab91b • 7 files, +408/-9
Pull a back chip in from the edge of the detail

A left-to-right swipe over the detail pane brings in a circular back chip and,
past 72px, navigates back. Only the chip moves: revealing the master would mean
measuring the whole chat list at the moment the finger starts moving, since it is
collapsed while a chat is open, and a Frame navigation cannot be scrubbed anyway.

MessageSelector already owns a horizontal tracker over every bubble, and it wins
the manipulation: its source claims the contact first and chaining is off. So the
MasterDetailView does not compete for it. It owns the chip and binds it, by
expression, to whichever tracker is driving - MessageSelector's over a bubble, its
own everywhere else. Expressions may reference a tracker from anywhere in the
compositor, so nothing runs per frame on the UI thread.

The bubble already stays still under such a swipe: its offset expression reads
CanShare, which is false whenever back has the direction. Only MinPosition was
holding it at zero.

Back takes the direction Share is not using, so a user who wants it everywhere
turns Share off, and no setting is ever on while doing nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

UnigramDev/Unigram/develop • ff6dd5a • 4 files, +85/-17
Make the back chip harder to miss

Fela asked for something catchier. It is 40px rather than 30 and travels the
full width of its own diameter, it swings upright from -30 as it comes in, and
past the threshold it latches into an armed state - scale pops to 1.15 and
opacity goes to full - so releasing feels committed rather than guessed at.

The tracker is clamped at the threshold, so progress rests at exactly 1 for as
long as the gesture is past it. Testing that rather than a distance means the
armed state latches on and stays on, instead of flickering at the boundary.

Still one expression per property, so none of this costs a frame.

The fill colour is now refreshed per gesture. The chip is built once and lives
for the window, so it kept whatever accent it was born under across a theme
change.

Carries the generated Resources.cs and .resw for the SwipeGoBack string added
in the previous commit.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

#unigram