UnigramDev/Unigram/develop • d4a7992 • 2 files, +38/-53 Drop the second interaction source the scrol

UnigramDev/Unigram/develop • d4a7992 • 2 files, +38/-53
Drop the second interaction source the scroll mode made unnecessary

It was placed inside the scrolling host's content back when a scroller taking the
pan looked like the cause. It is not: once the manipulation is held open, an
ancestor source is reached over the content, which is what SettingsStickersPage
has been demonstrating all along - it works on nothing but the DetailRoot source,
its TableListView host never having been given one.

So the method keeps only the VerticalScrollMode it holds open, and no longer has
to reach the host's content element at all.

Two dead visual properties go with it. The sprite's CenterPoint was left from
when it was scaled on its own, and the container's Size does nothing on a
ContainerVisual, which draws nothing and carries no clip. The container's
CenterPoint stays and is now explained: mirroring runs through the X scale, so
the centre has to be the circle's.

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

UnigramDev/Unigram/develop • 6e51c6f • 3 files, +31/-5
Ask for the back gesture rather than let it be brushed into

72 was borrowed from the reply and folder swipes, and at that distance it fired by
accident. Those two are cheap to trigger and cheap to undo. Leaving the page is
neither, so it now wants 120.

The threshold is public, because MessageSelector has to clamp its own tracker to
the same figure whenever back is what the left-to-right direction does. Left at
72 there, the pull would commit while the indicator was still a little over half
drawn - the tracker would reach its bound long before progress reached 1.

Share keeps 72, since it shares that direction only when back is not using it.

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

UnigramDev/Unigram/develop • 412f875 • 1 files, +8/-3
Guard the location access request in CheckDeviceAccessAsync

Geolocator.RequestAccessAsync is a call into the Windows Geolocation
Service and throws ERROR_SERVICE_DISABLED (0x80070422) when that service
is disabled, as the identical call in SendLocationPopup.FindLocation did
in the field. Treat a throw as access not being available, the way
StartTrackingAsync already does.

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

UnigramDev/Unigram/develop • 4290dae • 1 files, +13/-4
Refuse a drag whose data view cannot be inspected

IDataPackageView::Contains is a cross-process call into the process that
started the drag, and it can be denied, or fail because that process went
away mid-drag. Neither is something the app can act on, so the drop is
declined and the failure logged.

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

#unigram