Fix invalid min/max sizes of global areas after loading factory settings

Simply loading factory settings and dragging an area separator
immediately after would cause an assert because of these invalid sizes.

Seems that since rB07499c04f612 we correctly initialize DPI related
UserPref values with 0, which caused DPI dependant initialization of
global areas to set ScrArea.global.size_min/max to 0 too.
This commit is contained in:
Julian Eisel 2020-01-14 18:48:58 +01:00
parent 2a638e8c90
commit e4bf08a363
1 changed files with 2 additions and 0 deletions

View File

@ -702,6 +702,8 @@ static void wm_window_ghostwindow_ensure(wmWindowManager *wm, wmWindow *win, boo
/* happens after fileread */
wm_window_ensure_eventstate(win);
WM_window_set_dpi(win);
}
/* add keymap handlers (1 handler for all keys in map!) */