-
-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cursor scaling issues after aquamarine #7162
Comments
bisect please |
The issue has been happening since aquamarine was merged, I will try to bisect inside of the aquamarine PR. |
odd because on my laptop all is good and I use 1.5 |
I tried with a commit in the middle of the aquamarine pr and got the same, now I'm far from the laptop and partially drunk so I'll keep binary searching when I go back home. |
I was trying to bisect but given that during aquamarine development, you were updating all the components in parallel it's very hard to know when the error happened for the first time (as I can't compile some commits cause nix was broken at that point). For what I managed to test: |
I've found it, 1d4e518 (in move to aquamarine MR) is the first bad commit. Building 5dd2c27 + aquamarine a70fc6a (latest atm) with
Completely fixes the scaling problem for me, regardless of values of Not sure if it's a proper fix though. All the bisecting is on aquamarine 0ab8ffa, a bit outdated, because I initially misremembered that the cursor was fine until recently, and tried to see if it was aquamarine that broke it. It wasn't fine. It's just that the issue only manifests for me when hovering over swaybg. DetailsCursor: BAD 8a5f9bb keybinds: handle null monitor in pinActive (7122) BAD r5027.cc7c117f-1 - pre-locks pr? Further: BAD 8a5f9bb keybinds: handle null monitor in pinActive (7122) Further: BAD 016da23 move to aquamarine Bisecting the aquamarine MR: BAD 4b84029 rerun pipeline FAIL means
Attempting to BAD d786094 stuff Attempting to BAD 95ddf9e stuff for aq alloc split Result: 1d4e518 is first bad commit. |
does #7178 fix this> |
@gulafaran can you integrate this to #7178? seems to make sense |
will do |
pushed to #7178 , added a size check inside getShape and reload theme incase scale changed. should get the previous behaviour back. |
With default However, when
|
il see if i can reproduce tomorrow its getting late heh
artifacts at all times, and 2 times bigger at all times or do i need two monitors with different scaling to reproduce? thought id ask and il see if i can reproduce it |
Artifacts as soon as I set Two times bigger immediately after setting Those are two separate effects that can be combined when the said options are both So yes, at all times as soon as options are set. |
thanks il see what i can find <3 |
does it occur on #7178 now? there was a heap use after free going on |
No, it's fixed completely in both cases. cursor.mp4 |
nice :) |
Regression?
Yes
System Info and Version
Hyprland in master
Description
After aquamarine cursors rendered by hyprland don't scale with the monitor.
How to reproduce
If you have both
HYPRCURSOR_SIZE
andXCURSOR_SIZE
set to 16 and you scale the monitor to 2 the XCursors looks fine but the hyprcursors looks tiny.One can workaround it by setting HYPRCURSOR_SIZE to
2 * XCURSOR_SIZE
but that will break in other monitors.Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: