Flutter 3.50 deprecates its built-in Material and Cupertino libraries in
favour of the material_ui and cupertino_ui packages. The imports move
with the official fix (dart fix, migrate_design_widgets); the app's old
two-library theme bridge collapses into one Theme type.
- MaterialExpressiveScope keeps the complete host theme nearest its
child. The reduced copy made for the expressive widgets now shares the
app's Theme type and would hide component themes and extensions.
- LegacyThemeBrightness hands the brightness to the glass package, which
still reads Flutter's built-in theme.
- appLocalizationsDelegates lists the material_ui localization delegates;
the generated list still names the built-in ones.
- Tests: findByTooltip and pageBack replace the flutter_test helpers that
only know the built-in widgets, and several tests that had gone stale
against earlier app changes are repaired.
A lock toggle in the queue header of both styles, also in the Queue
section of Playback settings (where search finds it), saved as the
`queueLocked` setting. While it is on, the queue UIs offer no drag
handles (Material's long-press drag included) and no swipe to remove,
and a reorder that still arrives is ignored. Tapping a song still plays
it, and adding songs from elsewhere (Add to queue, Play next, Autoplay,
a paired device) still works. Neither queue UI has a Clear action, so
there was none to block.
Material: an M3 Expressive toggle icon button (`ExpressiveIconButton`,
selected state) before the Autoplay, Repeat and Shuffle toggles of the
Up next header, in the phone sheet and the desktop inspector. Mornye: a
44 pt icon toggle at the end of the Continue Playing title row, filled
while locked like the queue's mode buttons, on phones and desktop.
The lock covers this device's queue UI only; edits a paired phone sends
to the computer's queue are not blocked by the computer's lock.
A No duplicates in queue switch in a new Queue section of Playback
settings, off by default. While it is on, Add to queue, Play next and
adding many songs move an entry already coming up instead of queueing a
second copy, and a batch adds each song once, in its order. The song
playing and the songs before it are never touched, so they can be
queued again.
Identity is where a song plays from (`queueIdentityKey`), not its id or
tags: one file has different ids in the Library, the download history
and a plain path, while a FLAC and an MP3 copy share their tags and are
both meant to be queued. A `file://` URI counts as its path, a SAF
document is matched by provider and document id so a folder-tree URI of
it matches too, and `network://` sources (NAS, Subsonic, a paired
device) and CUE tracks name one song each. Stream URLs compare as is:
one with a fresh token never matches, which keeps a copy rather than
merging two songs.
Every path that adds to the queue goes through `enqueue` and
`enqueueAll`, so Link follows the playing device's own setting: songs a
phone queues on the computer, and a computer queueing a phone's songs
there. Autoplay already leaves out songs coming up and is unchanged.
The moved entry is removed without marking it dismissed for Autoplay,
and the shuffle order and play history follow the removal.