From e4bf08a363d98bf2bd3012349b314570e6e86dba Mon Sep 17 00:00:00 2001 From: Julian Eisel Date: Tue, 14 Jan 2020 18:48:58 +0100 Subject: [PATCH] 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. --- source/blender/windowmanager/intern/wm_window.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/blender/windowmanager/intern/wm_window.c b/source/blender/windowmanager/intern/wm_window.c index e68d4902c66..a711b35e2c9 100644 --- a/source/blender/windowmanager/intern/wm_window.c +++ b/source/blender/windowmanager/intern/wm_window.c @@ -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!) */