HyDE icon indicating copy to clipboard operation
HyDE copied to clipboard

[Bug]: rofi position is wrong when monitor is in portrait mode - vertitcal monitors

Open fibsussy opened this issue 5 months ago • 1 comments

Description

when I open up clipboard history (cliphist.sh) the position is predictably around the cursor, which is as expected. This works great in normal single-monitor landscape (I only have 1 monitor so idk about multiple)

When I flip my monitor to portrait mode, the clipboard history will spawn in unpredictable locations sometimes. Sometimes completely off screen, wrapping, just not as expected

I mention clipboard history because this is how I found it but this is an issue for all rofi windows that use the cursor for positioning. Example emoji, glyph,

Steps to Reproduce

  1. Flip your monitor to portrait

either

monitor = eDP-1, highres highrr, auto, 1, transform, 1

or what I had (I tested without my bind but im putting it bc its convenient)

bind = $mainMod, U, exec, ~/Scripts/hyprland_toggle_portrait.sh
#!/bin/bash

read name transform < <(hyprctl monitors -j | jq -r '.[] | select(.focused) | "\(.name) \(.transform)"')
hyprctl keyword monitor $name, highres highrr, auto, 1, transform, $((1 - transform))
  1. Put your cursor in the bottom right of the screen (this is where its the most buggy 3.Watch as you try to spawn clipboard history with Super+V, it never spawns anywhere neatly.

Expected Behavior

The clipboard history should have predictable behavior in portrait mode, just as it does in landscape mode

Actual Behavior

The clipboard history spawns unpredictably in portrait mode, but works correctly in landscape

Screenshots

No response

Environment

hyprland_systeminfo.txt

Additional Information

My prediction is that when it flips to portrait mode, it doesn't switch to using 1080x1920 for its calculations for where to put the position of rofi, but instead lingers on using 1920x1080.

This is likely why its buggy towards the bottom right instead of the top left.

fibsussy avatar Jul 12 '25 23:07 fibsussy

I am aware about this and the fix for this was not accepted during the hyprdots era. I will try to fix this no on this branch. Thanks

can you also please provide the output of hyprctl monitors ?

kRHYME7 avatar Jul 13 '25 05:07 kRHYME7