hypr/apps: open DaVinci Resolve's main window fullscreen so it isn't covered by the bar - #6429
Closed
28allday wants to merge 1 commit into
Closed
hypr/apps: open DaVinci Resolve's main window fullscreen so it isn't covered by the bar#642928allday wants to merge 1 commit into
28allday wants to merge 1 commit into
Conversation
…r it Resolve's floating main window places itself at 0,0 at full monitor size, ignoring the bar's exclusive zone, so the bar draws over Resolve's own menu bar. Fullscreen renders above top-layer surfaces, which puts Resolve over the bar instead of under it. Scoped by title so the splash, Project Manager and modal dialogs keep their natural size.
28allday
added a commit
to 28allday/DaVinci-Resolve-Omarchy
that referenced
this pull request
Jul 29, 2026
…ranch PRs basecamp/omarchy#6429 and #6430. Both target `quattro` — upstream `master` is still Omarchy 3 and has no default/hypr/apps/davinci-resolve.lua at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts Hyprland window rules for DaVinci Resolve so that the main Resolve window opens fullscreen, ensuring it renders above Omarchy’s top-layer bar (avoiding the bar covering Resolve’s own menu bar) while keeping other Resolve windows (splash, Project Manager, dialogs) at their natural floating sizes.
Changes:
- Add a title-scoped window rule that sets fullscreen only for windows titled
DaVinci Resolve - <project>. - Document why fullscreen is used (layer ordering vs reserved zones) and why the title match must be narrow.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Symptom
On Omarchy 4.x, launching DaVinci Resolve leaves Resolve's own menu bar (File / Edit / Trim / Timeline / Clip / …) hidden underneath the Omarchy status bar, so those menus cannot be clicked.
Root cause
omarchy-baris a layer-shell surface on Hyprland'stoplayer with a 26px exclusive zone:That reserved zone only constrains tiled windows, and it is being honoured correctly —
hyprctl monitorsreportsreserved: [0, 26, 0, 0], and tiled windows start at y=38 as expected.The problem is that Resolve is not tiled.
default/hypr/apps/davinci-resolve.luafloats every Resolve window, which is the right call — Resolve's many child windows tile badly. But floating windows are positioned by the client, and Resolve's XWayland main window places itself at 0,0 at the full monitor size, ignoring the reserved zone entirely:So the bar, being on the
toplayer, draws over it.Fix
Hyprland renders a fullscreen window above
top-layer layer-shell surfaces. Opening Resolve's main window fullscreen therefore puts Resolve over the bar instead of under it. The bar is not modified, hidden, or killed — it behaves normally again as soon as you leave fullscreen or focus another window.Why the title match must be narrow
Every Resolve window shares the same class, and only the main one may be fullscreened. Windows observed during a cold start:
resolveProject ManagerPreferencesDaVinci Resolve - <project name>Requiring the
" - <project>"suffix leaves the splash, the Project Manager and Resolve's modal dialogs floating at their natural size. A class-only rule would fullscreen all of them, which is why the rule is title-scoped.The class pattern
.*[Rr]esolve.*is kept byte-identical to the existing rule in this file for consistency; the title is what does the scoping.Verification
Tested on Hyprland 0.56.1 / Omarchy 4.0.0.r1440, NVIDIA, 2560×1440 logical (3840×2160 physical, scale 1.5), DaVinci Resolve 21.0.3.
Method: sample the top 26px strip with
grim. Bar colour is(26,27,38); Resolve's UI chrome is(23,24,26).Before — bar covers Resolve:
After — Resolve renders over the bar, its menu text now visible at y=35:
With the exact rule string in this PR installed, a cold start produces precisely the intended scoping — only the main window is fullscreened, and a modal dialog that happened to open during the run was correctly left alone:
That
Preferencesline is the important one: it is the failure mode a class-only rule would produce (a 630×534 dialog blown up to fill the screen), and it demonstrably does not happen.Notes for review
SUPER + F.omarchy toggle bar offand restore it on exit. It needs no window titles, but hides the bar system-wide across all workspaces for as long as Resolve is open, and leaves the bar hidden if the process is killed uncleanly.