Mercurial > vim
view pixmaps/error.xpm @ 33424:14cf0b014b99 v9.0.1970
patch 9.0.1970: win32: high-dpi support can be improved
Commit: https://github.com/vim/vim/commit/7086b3e76a81cf87592077d54e0ef46a60006c2c
Author: Ken Takata <kentkt@csc.jp>
Date: Mon Oct 2 21:26:03 2023 +0200
patch 9.0.1970: win32: high-dpi support can be improved
Problem: win32: high-dpi support can be improved
Solution: implement WM_GETDPISCALEDSIZE
win32: Better support of Per-Monitor V2 High DPI
Implement WM_GETDPISCALEDSIZE.
It is not so easy to calculate the new size without actually changing
the size. So, this returns an approximate size.
This doesn't work well when a bitmap font (e.g. FixedSys) is selected,
but I think this is acceptable.
closes: #11812
closes: #13252
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Ken Takata <kentkt@csc.jp>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Mon, 02 Oct 2023 21:30:05 +0200 |
parents | 3fc0f57ecb91 |
children |
line wrap: on
line source
/* XPM */ static char * error_xpm[] = { /* width height ncolors cpp [x_hot y_hot] */ "34 34 4 1 0 0", /* colors */ " s none m none c none", ". s iconColor3 m black c #FF0000", "X s bottomShadowColor m black c #5D6069", "o s iconColor2 m white c #FFFFFF", /* pixels */ " ", " ........ ", " ............ ", " ................ ", " .................. ", " ....................X ", " ......................X ", " ........................X ", " .......o..........o.......X ", " ......ooo........ooo......X ", " ......ooooo......ooooo......X ", " .......ooooo....ooooo.......X ", " .........ooooo..ooooo.........X ", " ..........oooooooooo..........X ", " ...........oooooooo...........XX ", " ............oooooo............XX ", " ............oooooo............XX ", " ...........oooooooo...........XX ", " ..........oooooooooo..........XX ", " .........ooooo..ooooo.........XX ", " .......ooooo....ooooo.......XX ", " ......ooooo......ooooo......XX ", " ......ooo........ooo......XXX ", " .......o..........o.......XX ", " ........................XXX ", " ......................XXX ", " X....................XXX ", " X..................XXX ", " X................XXX ", " XX............XXXX ", " XX........XXXXX ", " XXXXXXXXXXX ", " XXXXXXX ", " "};