Switching to a tray menu whose items were not currently loaded
collapsed fullHeight at the instant of the switch, so the chrome
morphed DOWN to a stub and replayed the vertical grow when the items
landed, rather than moving across from the previous panel.
An empty Card is not height 0 but 2*cardPad, so loaded-ness has to come
from the model: menuLoaded tracks menuOpener.children. While a newly
assigned menu is loading, fullHeight holds the last loaded height, so
the morph stays continuous and the correction on arrival is small —
nil when it is the same menu as last time.
ui.nix radius knob at 20.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
contextMenu nulled menuOpener.menu whenever it hid, throwing away the
loaded items. The only thing that refills them is the hover prefetch,
which fires on enter — and the cursor is already on the icon you just
clicked, so closing and reopening never re-triggered it. The reopen
re-fetched over DBus and the panel grew to its empty height, then
jumped when the items arrived. Moving to another widget and back
worked only because it produced a fresh hover-enter.
Keeping the handle assigned makes reopening the same item free, and
since assigning an unchanged QML property is a no-op it also covers
switching away and back. openFor() reassigns for a different item.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
seedFromButton went back to snapping only long enough to place the
stub, then releasing so tY/tH/openW all animate out to target. Holding
the snap through the grow pinned the height to its final value, so
panels slid out already full height instead of growing from the icon.
With the seed gate fixed in the previous commit, the three paths are
the ones the top bar had: open from closed seeds a stub at the widget
and grows both axes, close shrinks back to that stub, and switching
between dropdowns skips the seed so the bindings just retarget and the
panel morphs from one shape into the next.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Revert the wait-for-items delay: never block opening on the menu.
The actual bug was in the rotation. toggleDropdown gated seeding on
chrome.height < 0.5, correct when height was the growth axis, but the
growth axis is width now and chrome.height is tH — never 0 (200 by
default, 32 after shrinkToButton). So seedFromButton has not run since
the bar went vertical: the chrome never seeded at the clicked widget
and tH animated from whatever the previous dropdown left behind.
Gate now tests chrome.width. seedFromButton also holds snap for the
length of the grow instead of releasing it immediately, so the panel
expands along one axis at its content's real height, and content that
lands mid-grow is followed instantly rather than starting a second
animation.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The DBus menu populates asynchronously and Steam's is slow, so the
panel was sized from an empty body: menuItems.width is fixed, making
the width final immediately while fullHeight was only padding. The
panel shot out sideways, then lurched taller when the items arrived —
two motions instead of one.
contextMenu now loads the menu first and opens once it has items,
falling back to a 500ms timeout so a menu that never populates cannot
strand the click. Hovering a tray icon also prefetches its menu, which
covers the wait in practice since you cannot click without hovering.
Clicking the open menu's own icon still closes it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Panels buried only 8px into the bar while their corner radius was 24,
so 16px of rounded corner stuck out past the joint: the outline pinched
where the corner turned, then the fillet bulged back out. That is the
balloon at the connection point.
meltInto now tracks Theme.radius, so the whole corner ends up inside
the band it merges with and only straight edges reach the junction —
which is what smin is meant to fillet. Applies to the panel, toast and
launcher. meltK follows radius / 2 so the fillet scales with the one
rounding knob instead of drifting out of step.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
New settings/ui.nix holds `radius` as the one source of truth. Theme
derives radiusCard/Small/Tiny from it and hyprland's decoration.rounding
reads the same value, so one number rescales the whole desktop —
previously the shell and the window corners were unrelated constants,
which is why doubling Theme.radius left windows at 8.
Cards were using the SAME radius as the panel containing them. Nested
corners need outer − gap; matching them makes the inner corner
over-round for its size, which is the inflated/balloon look. All nine
inner surfaces now use radiusCard (radius − panelGap). Invisible at
r=8, obvious at r=32.
Radius 32 -> 24.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Radii doubled a second time (32/24/16).
Dropdown panels were +16 on the cross axis while the shader insets 8
top and bottom, leaving the panel edge flush with the content (0
padding) against a 4px overhang on the growth axis. Now +24 with the
content offset 12, giving 4px above and below to match the right.
Session menu becomes a real BarDropdown instead of its own surface:
it shares the morphing chrome with the other bar menus, so switching
between it and e.g. volume glides rather than cross-fading. Drops its
dedicated SDF surface, shader uniform and mask region, and the power
button gains the same hover-to-switch the other widgets have. Moved
beside volDropdown so it sits after the component declaration.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Panels near a frame band left a visible seam instead of merging. The
clamp now targets the frame's inner edge and the shader extends any
surface within snapDist 4px INTO the band, so the SDF fuses them into
one swollen shape — the launcher's launchBot trick, generalised to
dropdowns, the session menu and the toast.
Reverts the panelGap inset from the previous commit, which pushed in
the wrong direction.
qsIcon used anchors.verticalCenter and was centred only because the
cell was qsIcon.width; at barWidth it sat at x=0.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
trayArea kept anchors.verticalCenter from when it was a Row inside a
Row. A Column refuses to position ANY child when one sets a vertical
anchor ("Column will not function"), so volume/network/night-mode/
tray/power all fell to y=0 and stacked unclickably in the corner.
Workspace switch animation gets style = "slidevert" so it slides up/
down to match the vertical workspace column.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A dropdown that hits the clamp landed exactly on frameWidth, fusing
into the frame band in the SDF and losing its rounded corner — that
is what the calendar was doing at the top. Clamp now insets by
panelGap at both ends.
Bottom cluster spacing 12 -> 16, separators 5 -> 10.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Calendar was left on dropdownY: bar.height / 2 from the rotation, so
it opened at screen centre instead of next to the clock it comes from.
It now maps the clock's position like every other dropdown.
Bottom cluster reads as one clump: bumped its spacing to 12 to match
the top and split status icons / tray / power with separators.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Bar moves from a horizontal top band to a vertical left column
(Theme.barHeight -> barWidth, 46px for the stacked HH/mm clock).
Every panel now grows rightward out of the bar instead of down:
the dropdown chrome's morph axis, the SDF surface geometry and the
session menu all swap x/y. The launcher is the one surface left at
bottom-centre, as asked.
New: NixOS snowflake at the top (recoloured to the accent with the
tray's hidden-Image + ColorOverlay trick), vertical workspace dots
whose focused pill grows on height, an inline OSD slot in the gap
between the two clusters, and a power button in the bottom-left
that opens the session menu.
Dropped the flush-to-far-edge dropdown special case — clamped
tracking plus the SDF melt already covers it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sixth surface in the SDF chrome shader, melting out of the bottom
frame. Volume is reactive via Pipewire so the OSD also fires for
pavucontrol/mixer changes; brightness routes through a new osd IPC
handler since sysfs backlight only notifies via POLLPRI.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>