mirror of
https://github.com/AvengeMedia/DankMaterialShell.git
synced 2026-10-26 21:17:47 -04:00
Marlon Kranz
579d6f7b5c
Opening the launcher by hovering the frame edge requested the Overlay layer via CompositorService.framePeerSurfacesUseOverlayForScreen(), which resolves to whether the frame is configured for the screen and is true in normal use. DankLauncherV2ModalConnected's frameOwnsConnectedChrome requires the Top layer, so the overlay request silently dropped connected-chrome anchoring: the launcher opened dead-centered with a different animation instead of emerging from the configured frame side. The keybind/bar-button path already opens on the Top layer by passing no overlay argument. The edge-hover trigger only runs in connected frame mode to begin with (gated by usesConnectedFrameChromeForScreen in this file's own eligible check), so there's no case where it needs standalone/overlay behavior. Match the keybind path.