Treat Recordly's recording toolbar as a HUD - #11157
Open
ReidenXerx wants to merge 1 commit into
Open
ReidenXerx wants to merge 1 commit into
ReidenXerx wants to merge 1 commit into
Conversation
Recordly draws a small opaque pill inside a much larger transparent Electron surface. Two defaults work against that shape: the default-opacity tag compounds with the app's own alpha until the desktop reads through the controls, and the standard border is drawn around the whole surface, outlining a large empty rectangle around a small toolbar. Give it the treatment webcam-overlay and hermes already get: drop the opacity tag, force full opacity, and remove the border and shadow. Pin it, because the stop button has to stay reachable from whatever workspace you switch to while recording, and skip initial focus so a toolbar appearing mid-sentence does not take the keystrokes. Matched on title rather than class alone. Recordly's editor is an ordinary window that should keep tiling and keep its border, and it shares the class with the toolbar. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019yo64P8KJNrR6aGx5oYCTz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recordly (https://recordly.dev, AUR
recordly-bin) is an Electron screen recorder whose recording toolbar is a HUD: a small opaque pill painted inside a much larger transparent surface. Two Omarchy defaults work against that shape.windows.luatags every windowdefault-opacity("0.985 0.96"), which compounds with the app's own alpha until the desktop reads straight through the controls. And the standard border is drawn around the whole transparent surface, so a large empty rectangle is outlined around a small toolbar — which is what people notice first.This gives it the same treatment
webcam-overlay.luaandhermes.luaalready get for the same class of window.Matched on title, not class alone
Recordly's editor is an ordinary window that should keep tiling and keep its border, and it shares the class
recordlywith the toolbar:A class-only rule floats and de-borders the editor too. Scoping to
title = "^Recordly$"leaves the editor alone.Why pin and no_initial_focus
Both match
webcam-overlay.lua, and both matter for a recording toolbar specifically: the stop button has to stay reachable from whatever workspace you switch to mid-recording, and a toolbar that appears while you are typing must not take the keystrokes. Happy to drop either if you would rather keep the change minimal.Testing
Verified live on Hyprland 0.56.2 with
recordly-bin1.4.0:pinned=true,floating=trueconfirmed viahyprctl clients.Note window rules apply at map time, so
hyprctl reloaddoes not retrofit them onto an already-open window — the app has to be restarted to see the effect.Not covered
Recordly shows a third surface when the webcam is enabled (a ~200x200 bubble, same class). I only saw it briefly and did not capture its title, so I have deliberately not shipped a guessed selector for it. If it needs the same treatment, it is a one-line addition once someone reads the real title.