44 Commits

  • Lyrics and the control centre IPC, fitted to this version
    The media panel's Lyrics button (#109) gets a switch of its own,
    mediaLyrics, on the media module's card in edit mode, on by default; the
    title beside the buttons takes back the room when it is off. The IPC
    target still opens the page either way. CHANGELOG: the four pulled PRs
    from GitHub's main, #108 and #109 under Unreleased.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Merge pull request #90 from ciroenrique4-eng/pr/system-panel
    feat(control centre): a bento grid you lay out in its own editor, and tiles of your own
  • OSD: with the dock a notch too, the dock itself turns into it
    When the OSD and the dock are both notches, the OSD no longer rises as a notch of its own beside a dock stepping down for it. A dock on screen morphs into the card in place, its icons handing over to the card's content as it narrows, and morphs back after; one tucked away rises out of the edge already the card, sinks back as it, and turns back into the dock out of sight. A change of kind while it shows, volume to Caps Lock say, morphs the dock from one card to the other.
    
    The card's content moves into OsdFace, so the card and the dock draw the same thing. The launcher opened over it takes the dock back as usual, and a dock under the pointer, busy or in edit mode keeps its icons while the card floats above it.
    
    It is on by default and has a switch: General > On-screen display > Morph the dock. Off, the OSD rises as its own notch as before.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Control centre: the pencil opens the layout in Settings, and tiles of your own
    The pencil in the panel's header opened the old in-panel tile editor, which
    knew only the small tiles; it now closes the panel and opens Settings on the
    System module's layout, and the in-panel editor is gone.
    
    Your own tiles, under the layout: a name, an icon from those Lucid carries,
    and commands run through bash. One command makes a button; one to turn it
    off too makes a switch, kept right by an optional check (exit 0 = on) each
    time the panel opens, as game mode is. A new one goes onto the panel; they
    join the tile catalogue, so the shelf offers them like any other.
    
    The grid now saves only the heights given by hand. It saved what each block
    needed at the time, so one that later held less kept the room.
  • Control centre: five blocks, drawn alike in the panel and its editor
    The pieces (big and small tiles, standing and lying sliders, the media card and
    the gauges) move to lucidcc, and CcBlock lays out any block from them; the panel
    and the editor on the module's card both use it, the editor with made-up
    readings and the whole grid scaled down, so the two can no longer drift apart.
    The big tiles and the small ones are blocks of their own, as are media and the
    gauges; a tile is dragged or tapped across from one tile block to the other.
    The three blocks there were are read as the five and written out once the
    layout is edited. A block given more room than it needs fills it: standing
    sliders stretch, lying ones and the gauges spread out, the media card keeps to
    the middle. Cards behind every block, an option, puts the tiles and the sliders
    on a card as media and the gauges are.
  • Control centre: one bento grid, rows that are thin strips
    Stacked and Wide are gone: the single column is now just the grid's first
    layout, six tiles wide with the blocks one under another, and the module's card
    lays it out any other way. A row is a thin strip instead of as tall as its
    tallest block, so a block is as tall as it is made, never less than its pieces
    need; one that grows pushes those under it down. The editor draws the blocks as
    the panel does, with their buttons in a bar above the grid: a block is carried
    by anything but its pieces and stretched by any edge or corner. When the grid
    is wider than the screen the panel falls back to the single column.
  • Control centre: the wide panel as a bento grid
    Its blocks sit at a column and row of their own and span as many of each as
    they are given, so one can go under another, not only beside it. A column is a
    tile wide; a row is as tall as the tallest block sitting in it alone. On the
    module's card the editor draws the grid: a block is carried by its handle to any
    cell (one it lands on takes its old place), stretched by its corner, and the
    sliders can lie down or stand up. Empty rows and columns fold away in the panel.
    The layout is kept in systemGrid; left empty, the blocks sit side by side as
    before.
  • Control centre: blocks built like bricks, big and small tiles, standing sliders
    The panel is now three blocks, each holding pieces:
    
    - Sliders: brightness, volume (with its output button) and, new, the
      microphone. Lying down one under another; standing up side by side in
      the wide panel, as tall as the tallest block beside them.
    - Toggles: the tiles. A tile is small (a cell) or big (half a row, with its
      name and what it is doing), so the big ones are no longer a second list
      repeating the grid. Wi-Fi and Bluetooth are tiles of it now, big by
      default; until the tiles are edited they lead the grid, so a list saved
      before keeps them. The panel's own editor, and its Reset, know them.
    - System: media and the gauges, each run of gauges on one card.
    
    Stacked puts the blocks one under another, Wide side by side.
    
    The Layout row on the module's card (PanelBuilder) draws the blocks as the
    panel lays them. A block is dragged by its handle, carrying what it holds,
    and hidden with its eye; inside one the pieces are dragged into order,
    taken out with their cross and put back from its +. A tap makes a tile big
    or small. The Sections, Big tiles and Gauges lists go.
  • Control centre: a wide panel, and what it holds picked on its card
    The System module's card gains an Opened look and four lists to pick from
    and put in order:
    
    - Stacked or Wide. Stacked is the panel as it is. Wide spreads it over
      three columns: Wi-Fi, Bluetooth and the tiles (as wide as the single
      column, so they look the same), the sliders and media, then the machine
      with its gauges two to a row. A column with nothing in it goes; with one
      left, or on a screen too narrow for it, the panel stays a single column.
      Only the main view is wide: Wi-Fi, Bluetooth, the tile editor and the
      rest keep the usual width.
    - Sections: brightness, volume, big tiles, tiles, media and the system
      card, in any order and any of them off (at least one stays).
    - Big tiles: Wi-Fi and Bluetooth as they are, and any of airplane mode, do
      not disturb, stay awake, dark mode, location, microphone, game mode, the
      power profile, night light and VPN, with a line under the name saying
      what each is doing. Their icon switches them; the rest of the tile opens
      their page where they have one (no chevron where they don't).
    - Gauges: CPU, memory, disk and battery, any of them, in any order.
    - Header buttons: edit, settings, lock and power.
    
    A section with nothing to show (no backlight, nothing playing) still takes
    no room. The defaults keep the panel exactly as it was.
    
    OrderedPicker is the power module's action list made reusable.
  • OSD: a notch style, lock keys as toasts, and the keyboard light
    Three additions, all off or invisible by default:
    
    - OSD style: the island as it is, or a notch - the card sits flush on the
      bottom edge, rises out of it instead of popping, and hangs the dock's
      concave corners off its sides. One vertical anchor in both styles (the
      notch reaches the edge through the offset), since swapping anchors lets
      the anchor engine write the height and drop its binding.
    - Caps Lock, Num Lock and the microphone can be a toast instead of a card,
      for a machine where the OSD is in the way. The detection stays in the OSD,
      which reports through a signal; ToastEvents shows it.
    - The keyboard backlight. Its key is handled in firmware: the led moves and
      nothing writes the file, so inotify never fires. kbd-backlight-watch.py
      sits in poll() on brightness_hw_changed and reports the level; the file
      watch stays for a level something does write, rereading after 200 ms
      because the driver applies the write out of line. The helper treats
      ENODATA (no key pressed since boot) as "no level yet", arms
      PR_SET_PDEATHSIG so it dies with the shell, and leaves if the led goes.
      A few whole steps draw as one block per step, the steps that are on in
      full and the rest as a thin rail, with the count as the readout; a
      fine-grained level keeps the level track. It is news only, so the card
      takes no pointer for it.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Active window: one look, the Chip look removed
    Its card no longer has an In the bar row; windowModuleStyle is gone from
    Prefs and the defaults, and the pill draws the icon and the title plain.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: a start button
    The launcher from the bar, a click to open it or put it away, at the start
    of the left group. Five looks: Lucid's mark as on the dock, a grid of nine
    dots, the distribution's logo (the one os-release names, in the accent;
    Lucid's mark where there is none), the account picture, or the word Start
    on a chip. It lights up while the launcher is open.
    
    A module new to the arrangement goes to the end of its home group; this one
    is marked "first" in the registry and goes to the start of it. It has
    nothing to unfold, so BarPill gains opensOnHover for a pill that is only a
    button. Off by default.
  • Release v1.20.1
    Desktop icons, bar islands and a full bar, live wallpapers and four picker
    styles, files over Bluetooth with a pairing agent, a Startup page, fingerprint
    unlock on the lock and login screens, five new widgets, metric or imperial
    units, the Steam open/close loop fixed, and the right graphics drivers for
    Steam. Fifteen pull requests from Ciro Rivera and one from SKetU-l. The full
    notes are in CHANGELOG.md.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Merge #11: Sound: level meters, balance, a channel test and WirePlumber's settings
    On 1.20's Sound page: a peak meter under the output and the microphone
    volume (with a switch of its own, Level meters), balance with a way back
    to the centre, a Left/Right test, an application put back on the default
    device, and a Behaviour card for WirePlumber's own settings.
    
    Left out on purpose: the per-step volume click and the "Click"
    notification sound, since 1.20 has its own volume tick and its own set
    of notification sounds. Osd.qml and the notifications page stay as 1.20
    has them, and assets/volume-click.wav is not added.
    
    The meter's scale() became dbFraction(): a function by that name shadows
    the scale property every Item already has.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: #50's looks and options on 1.20's modules
    The merge of #44/#50 kept 1.20's module looks and left the rest of #50
    out. These come in now as choices on each module's card, every one
    defaulting to how 1.20 already looks:
    
    - Clock: One line and Two lines beside the accent chip, and the date's
      format (1.20's "Tue, 06/10", "Tue 6", "Tue 6 Oct", or the locale's own)
    - Media: Cover and Compact beside the turning disc, a large-cover panel,
      and switches to hide it while idle, drop the artist, cap the title's
      width, hide the play button and turn the volume wheel off
    - Workspaces: Numbers beside the dots, how many always show, and the
      wheel on or off. The wheel now goes through the MouseArea, as in #50:
      the WheelHandler beside it never received it
    - Notifications: a dot, or bell and count on an accent chip
    - Tray: every app's icon in the bar, the icons in the palette's colours,
      and a switch per app to keep it out
    
    Co-Authored-By: cirorivera <ciroriv@proton.me>
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Merge #54: Workspaces: show which display each workspace is on
    By MrZtone. On 1.20's module: the new values go through Theme.dp, the
    new-workspace tile wears the overview's own tile, and the display badge
    is the monitor symbol with the number in it rather than a drawn screen.
    
    The grouping is a setting, Settings > Displays > Workspaces > Group by
    display, on by default. With it off, or with one display, the bar and
    the overview are 1.20's: every slot shows and an empty one offers a +.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Merge #44, #50: arrange the bar's modules, and three new modules
    Settings > Bar takes Ciro's arrangement editor and module cards, and the
    bar's layout is his barLayout plus the show* switches, which is also
    what a 1.10.5 install already has. The bar itself keeps 1.20's placement:
    barHas, barZones and barKeysOf now read barLayout, so the eased
    reordering and the slot a leaving pill keeps work as before.
    
    The six modules keep their 1.20 looks: their looks and look options are
    left out of barModules, the card and the defaults. Privacy, Power and
    Active window come in as they are, off by default. The placement fixes
    from #44 (the notification stack and the tray menu on either side, a
    right click to the module's card) are applied to the 1.20 modules.
  • Merge #36, #38, #40: templates for every palette, the Colours page and the Palettes page
    # Conflicts:
    #	Theme.qml
    #	lucidbar/Theme.qml
    #	lucidprefs/NavGlyph.qml
    #	lucidprefs/Settings.qml
    #	lucidprefs/ThemePage.qml
    #	support/wallpaper/set-wallpaper.sh
  • Merge 1.10.5 (main) into 1.20
    1.20 branched at v1.1.0, so every PR built on main dragged all of 1.10.5
    along with it. This brings 1.10.5 in once, so a PR merged into 1.20 now
    only brings its own change.
    
    Where the two lines met:
    - Power: one singleton for the session actions (1.20) and the power
      profiles (1.10.5), plus Power.symbol() for the Icon surfaces
    - Control centre: game mode and the power profile are tiles in the
      editable grid (Edit tiles adds them); a right click on the power tile
      opens the profile list, a view now called "profile" so it no longer
      clashes with the session buttons' "power"; the keyboard layout chip
      sits on the compact strip
    - Keybinds: the editable keybinds.json from 1.10.5, with 1.20's
      SUPER+Escape session bind added to the shipped list; the page and its
      settings IPC moved to Prefs.settingsPages and SettingsHost
    - Widgets: 1.20's Chrono-backed timer and phone widget stay; thermals,
      network and games draw their glyphs as material symbols
    - Toasts: plain symbol names are accepted, so the event toasts no
      longer fall back to the info icon, and the detail text reads on the
      inverse surface
    - Symbol table rebuilt for the new names
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: looks for the privacy, power and window modules
    Privacy: a tinted mark for each thing in use, or one small dot in the
    colour of the most telling (red while the screen is shared).
    Power: the symbol, or the symbol on a circle in the accent; opened, one
    action to a row or three to a row with the name under each.
    Active window: the icon and the text on the bar, or on a chip tinted with
    the accent; what it reads gains "Icon only".
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the tray module's looks and options
    Collapsed to one icon and how many are running, as before, or each app's
    icon in the bar: a click activates it, the middle button its second
    action, the wheel scrolls it, a right click opens its menu, and a dot
    marks one asking for attention.
    
    Its card lists the apps in the tray now, each with a switch: one switched
    off stays out of the bar and the panel until it is switched back on.
    The icons can also take the shell's colours, in the bar and in the panel:
    grey from the text, or the palette's secondary, tertiary or accent. They are
    lifted and then tinted, so their light and shade stay and a logo on a
    coloured disc does not turn into a blob.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the system module's looks and options
    Icons and values, as before, or only the icons, narrower.
    
    Its card picks which indicators it shows before it is opened (network,
    Bluetooth, volume, microphone, battery; at least one stays). The panel
    has them all either way, and the keyboard layout sign keeps its own
    switch in the System module card.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the notifications module's looks and options
    The bell and how many are waiting, as before; the bell with a dot while
    any are; or the bell and the count together on a chip in the accent (the
    error colour while one is critical).
    
    Its card adds leaving the bar while nothing is waiting; it comes back
    with the first notification, and stays while Do not disturb is on.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the workspaces module's looks and options
    Dots, with the numbers on hover as before, or the numbers themselves in
    slots a size smaller than the hover's, the active one on the pill and an
    empty one's number quieter.
    
    Its card adds how many workspaces it always shows (six before; one past
    them still shows while it exists) and whether the wheel switches them.
    
    The wheel never switched workspaces: the WheelHandler on the pill's face
    never heard it past the MouseArea over it, so the MouseArea takes it now.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the media module's looks and options
    Bars that move with the music and the track, the album's cover and the
    track, or only the bars and the play button. Opened, the cover beside the
    track or across the top of the panel.
    
    Its card adds leaving the bar while nothing plays, the artist before the
    title, how long the track gets before it scrolls, the play button, and
    whether the wheel turns the player's volume.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: the clock's looks and options
    On one line, in two (the date small under the time; a coming reminder
    tints the date, since the bell has no room there) or with the time on an
    accent chip. Opened, the full panel or only the calendar, in a narrow one.
    
    Its card adds the seconds, whether the colon breathes, how the date reads
    (short, with the month, or in numbers as the locale writes them) and the
    temperature outside after the date. The date itself stays on the Date &
    Time page, and the date row says so while it is off.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: an active window module
    The focused window's app icon and title. Opened, it names the app and
    shows the whole title, floats or tiles the window, centres or pins a
    floating one, sends it fullscreen, moves it to another workspace without
    taking the view along, closes it, and lists the other windows on the
    workspace to switch to. Every action names the window by its address, so
    it lands on the one shown whatever has the focus by then; a switch or a
    move waits for the panel's focus grab to let go, since that hands the
    focus back.
    
    It hides on a workspace with no window, and a window focused before the
    shell started shows too. Its card picks what the pill reads (title, app
    or both) and how long it gets, and whether the wheel over it walks the
    windows on the workspace and a middle click closes the window, both of
    which work on the panel's top strip too when it opened on hover.
    
    Off by default.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: a power module
    Lock, suspend, hibernate (where logind says the machine can), log out,
    restart and shut down, from a pill of their own, under how long the
    machine has been up. Log out, restart and shut down take a second click
    within three seconds, so a stray one does nothing. The commands are the
    dock's and the lock screen's; log out goes through hl.dsp.exit() first,
    since a Lua config reads a plain "exit" as no dispatcher at all.
    
    Its card picks the actions and their order, and whether the second click
    and the uptime are there.
    
    Off by default.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: a privacy module
    Shows up only while something uses the microphone, the camera or the
    screen, with one mark for each, and opens on the apps behind them.
    
    - microphone: the recording streams fed by a microphone, going by their
      PipeWire links, so one recording a device's own output (a visualiser)
      or a loopback is told apart
    - camera: a camera node's PipeWire consumers, and any program that holds a
      /dev/video device open itself (checked every 3 s while the module is on)
    - screen: a video source that is not a camera, which the portal makes for
      each share, with the apps it feeds, and Lucid's own recording, which
      the panel can stop
    
    Its card picks what it watches, whether a toast names an app the moment
    it starts (Lucid's own recording is left out), and whether a quiet shield
    keeps its place in the bar while nothing is in use. The card gains a
    reset for a module's own options.
    
    Off by default.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Bar: arrange the modules in three groups
    Settings > Bar > Modules gets an "Arrangement" row: three lanes, one per
    group of the bar (against the left edge, around the middle, against the
    right edge), with a chip per module to drag along its lane or into
    another. The arrow keys move the focused chip too: left/right along the
    bar, crossing into the next group at an end, up/down between lanes.
    
    The order lives in a new barLayout pref (JSON with left/center/right
    lists). Its default is today's order, so nothing moves until someone
    drags. A module the pref leaves out goes back to the end of its home
    group and an unknown id is skipped, so every module always has a place.
    The show* switches stay as they are; a switched-off module keeps its
    place and its chip is dimmed.
    
    The bar already placed its modules as groups (the left one growing
    right, the right one anchored to the edge, the clock centred between
    them), so shell.qml now builds the three groups from the pref, and the
    centre one is centred and kept clear of the sides the way the clock was.
    Each pill's pop-up aligns to its group's side. Two spots assumed today's
    sides: the notification stack under the pill now anchors to the pill's
    outer edge for whichever side it sits on, and the tray's context menu is
    kept on screen when the tray sits at the right.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Colours: shape the generated palettes, and a theme from your own colour
    Matugen always built the wallpaper's palette the same way: its default
    tonal scheme, standard contrast, and the image's most dominant colour.
    The Colours page gets a card on top to change all three, and there is a
    new theme built from a single colour.
    
    - Your colour: a theme ("colour") whose whole palette matugen builds from
      one colour, typed as hex, picked from anywhere on screen with
      hyprpicker, or one of a few to start from. The wallpaper stays as it
      is. apply-colour.sh renders every template from it through
      render-templates.sh, like the wallpaper path; set-mode.sh rebuilds it
      in light or dark.
    - Style: matugen's nine scheme types, Tonal (its default) to
      Monochrome, for the wallpaper and for Your colour.
    - Contrast: -100% to +100%.
    - Colour from the wallpaper: the dominant colours matugen finds in the
      wallpaper (wallpaper-colours.sh), each shown as the accent it gives.
      The pick holds for that wallpaper only; another one starts from its
      most dominant again, since the second colour of one picture says
      nothing about another. An index the picture doesn't have falls back
      to its most dominant.
    
    matugen-options.sh reads the settings for the scripts. Settings passes
    a new value along in the environment, since prefs.json is written a
    moment after a change; anything invalid falls back to matugen's
    default. Two things matugen's help gets wrong: --source-color-index
    takes 0 to 3, not 0 to 4, and hyprpicker's -q silences the picked
    colour itself.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Toasts for what the machine does on its own
    The toast was only ever raised by something the user had just done. The
    machine changes plenty on its own — a charger goes in, headphones
    connect, the Wi-Fi comes back, the power profile drops — and none of it
    was said anywhere.
    
    - ToastEvents watches the keyboard layout, game mode, the battery and
      its charger, Bluetooth devices, Wi-Fi, the audio output, displays and
      the power profile. Each one has its own switch under Notifications >
      System events, and a Preview button runs one of each through the real
      queue
    - the toast grows a queue: events line up rather than cutting each other
      off, an entry can carry a quieter second line, an icon can be a name, a
      raw path or a Nerd Font glyph, and a newer event of the same kind
      replaces the one on screen in place. What the user does still cuts in
      at once
    - nothing is announced for the first few seconds, so a reload does not
      narrate the state it just read as if it were news
    - each watcher waits out its own settling: the charger 800 ms, Bluetooth
      1.5 s, Wi-Fi 4 s for a roam or a resume, and the audio output is not
      announced right after a Bluetooth device connected, since that is the
      same event twice
    
    Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
  • Control centre: keyboard layout, a power profile tile and game mode
    Three things the System pill could answer and did not:
    
    - the active keyboard layout beside the Wi-Fi icon on the compact face,
      read off the main keyboard and refreshed on Hyprland's activelayout
      event. Clicking it steps to the next layout. Switchable on the Bar page
    - a Power tile: a click steps through the power profiles the daemon
      offers, the chevron opens a view listing them with what each one is
      for, whether performance is being held back and why, and who is
      holding a profile. It writes PowerProfiles.profile, so it works with
      power-profiles-daemon and with tuned-ppd
    - a Game Mode tile, for whatever a machine needs doing before a game:
      the on and off commands are set on the Bar page and an optional status
      command (exit 0 means on) keeps the tile in step with a keybind that
      does the same thing. Without commands the tile opens Settings rather
      than pretending to work
    
    Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
  • Sound: level meters, balance, a channel test and WirePlumber's settings
    The page says what each device is set to but not what it is doing, so
    there is no way to tell a dead microphone from a quiet one without
    opening something else.
    
    - a live peak meter under the output and the input volume, on a dB scale
      with a short hold. On a Bluetooth headset the input meter waits for a
      Listen button, since recording from one switches it to call quality
    - balance for an output with a left and a right channel, with a button
      back to centre. The volume now reads and scales the loudest channel,
      so a balance set off centre survives a volume change
    - a Left/Right test through pw-play, or a single Play on a mono output
    - an application sent to a device can be put back on Default device:
      the move lives in the default metadata, so it is read from there and
      cleared there. A stream recording an output's monitor is not offered
      it, having no default to go back to
    - a tick when the volume settles, off by default
    - a Behaviour card for the WirePlumber settings behind all of this:
      remembering each application's volume and device, following the
      default, pausing when a device goes away, headset call mode and its
      quality/latency preference, and mono audio. Saved with
      wpctl settings --save, so they outlive a restart
    
    The meters record through streams of their own, which are named
    "quickshell" and stay out of the recording list. The filter is on the
    node name rather than on properties, which arrive after the node is
    bound and would drop it back out of the list.
    
    Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
  • Update v1.1.0
    The lock screen rebuilt on PAM, Lucid as the session's polkit agent, a Users
    and Accounts page, the notification centre, clipboard history in the launcher,
    an on-screen keyboard, an SDDM theme, light mode, and Vulkan on NVIDIA.
    
    Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
  • Ship the hypr and look support layer; detect pinned apps; drop SDDM
    - commit support/hypr (hyprland.lua + 12 modules) and support/look
      (kitty, starship), which were untracked and so never reached a clone
    - install.sh: seed pinned.json from installed .desktop files instead of a
      fixed list, so a fresh machine gets real icons not letter tiles
    - install.sh: correct noto-fonts-emoji, move awww to the repo list, and make
      a failed dependency step non-fatal so the shell still installs
    - Dock.qml: generic pinned fallback, no personal apps or absolute paths
    - Mpris/GeneralPage: ClippingRectangle instead of the Qt5Compat OpacityMask
    - remove SDDM handling entirely
    
    Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>