diff options
| author | Julian Eisel <julian@blender.org> | 2020-12-27 17:08:34 +0300 |
|---|---|---|
| committer | Julian Eisel <julian@blender.org> | 2020-12-27 17:11:26 +0300 |
| commit | e56fe477489e190cc43f3128088f2b402068b108 (patch) | |
| tree | ea0ce1a0b1a6df5f9d6ecc54945492b1d09c8288 | |
| parent | 7916c593048bff5d6e15f801c5bd832815768cf9 (diff) | |
Fix crash when saving render from temporarily maximized render window
Steps to reproduce were:
* Start with factory defaults
* Set "Render in" to "Maximized Area"
* Render
* Open "Save as"
* Click Cancel
Mistake in 78d2ce19c4fb. Was using the wrong area pointer, which I think
didn't make a difference in most cases, but here it did.
| -rw-r--r-- | source/blender/windowmanager/intern/wm_event_system.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/source/blender/windowmanager/intern/wm_event_system.c b/source/blender/windowmanager/intern/wm_event_system.c index 90aa6a92d3c..859336d0338 100644 --- a/source/blender/windowmanager/intern/wm_event_system.c +++ b/source/blender/windowmanager/intern/wm_event_system.c @@ -2263,7 +2263,7 @@ static int wm_handler_fileselect_do(bContext *C, continue; } - if (ctx_area->full) { + if (file_area->full) { /* Users should not be able to maximize/fullscreen an area in a temporary screen. So if * there's a maximized file browser in a temporary screen, it was likely opened by * #EVT_FILESELECT_FULL_OPEN. */ |