Added configurable scaling priorities in options. #277
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.
There are 3 ways you can account for scaling in Hyprland.
There are certain scenario where you only want Hyprland scaling to be accounted for. Other times you want only GDK scaling accounted for and finally in some cases you need both. In scenarios where you have a normal DPI monitor and you set GDK scaling, you would select GDK as the scaling priority. If you have a HiDPI display, you (most likely) want Hyprland scaling as priority. If you are high DPI AND have custom GDK scaling you MAY want both.
Since we can't just assume in hyprpanel, we now have an option to users configure the scaling priority in
Configuration General > Scaling > Scaling Priority
.The scaling determines where the dropdown menus spawn so it's important to have the right option selected so menus spawn next to where the button is clicked and the screen edges are accounted for propery.
closes #274