Mercurial > vim
view pixmaps/tb_maximize.xpm @ 18642:bbea1f108187 v8.1.2313
patch 8.1.2313: debugging where a delay comes from is not easy
Commit: https://github.com/vim/vim/commit/eda1da0c9a8db1400649629117e7d248c07735f7
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 17 17:06:33 2019 +0100
patch 8.1.2313: debugging where a delay comes from is not easy
Problem: Debugging where a delay comes from is not easy.
Solution: Use different values when calling ui_delay().
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 17 Nov 2019 17:15:04 +0100 |
parents | 3fc0f57ecb91 |
children |
line wrap: on
line source
/* XPM */ static char * tb_maximize_xpm[] = { /* width height ncolors cpp [x_hot y_hot] */ "18 18 5 1 0 0", /* colors */ " s none m none c none", ". s topShadowColor m none c #DCDEE5", "X s iconColor1 m black c #000000", "o s iconColor2 m none c #FFFFFF", "O s bottomShadowColor m black c #5D6069", /* pixels */ " ", " .XXXXXXXXXXX ", " .X....X...oX ", " .X..oXXX..oXO ", " .X.oXXXXX.oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X..XXXXX.oXO ", " .X...XXX..oXO ", " .XooooXooooXO ", " .XXXXXXXXXXXO ", " OOOOOOOOOO ", " "};