summaryrefslogtreecommitdiffstats
path: root/audio/out/ao_coreaudio_chmap.c
diff options
context:
space:
mode:
authorDudemanguy <random342@airmail.cc>2021-04-12 13:53:10 -0500
committerDudemanguy <random342@airmail.cc>2021-04-12 14:09:28 -0500
commit74f5d4940e38799cb92319e89c030195c5d4fe54 (patch)
tree187d7403037c61dc0a4c2d38d684621baa32031c /audio/out/ao_coreaudio_chmap.c
parentf1d0365a6f72b88f7427814f636863ae1656f72a (diff)
downloadmpv-74f5d4940e38799cb92319e89c030195c5d4fe54.tar.bz2
mpv-74f5d4940e38799cb92319e89c030195c5d4fe54.tar.xz
wayland: support the display-hidpi-scale property
So apparently this property had existed since 2019. Internally, it's used as a part of the console.lua script for scaling. Yours truly somehow didn't bat an eye at the fact that the text in the console was super small (made worse by the fact that xwayland does scale) and just ignored it for all this time. Oh well. To report dpi changes to mpv's core, we need to use VO_EVENT_DPI in a couple of places. One place is, of course, the surface listener if the scale value reported by the wayland server changes. The other place is in the very first reconfig since mpv's core will not find the correct scale value until we actually get a wl_output from the wayland server.
Diffstat (limited to 'audio/out/ao_coreaudio_chmap.c')
0 files changed, 0 insertions, 0 deletions