diff options
| author | Severin <eiseljulian@gmail.com> | 2018-06-29 03:04:46 +0300 |
|---|---|---|
| committer | Severin <eiseljulian@gmail.com> | 2018-06-29 03:23:59 +0300 |
| commit | be983295ea14af226b3c824a035ccee9d416c67f (patch) | |
| tree | ad395fba6f4f6a05de6cfce802febcf3542a046d /source/blender/editors/space_text/text_header.c | |
| parent | 4d39da1060105210a665e083b8d035f18b989a9f (diff) | |
Fix: Moving area edge could corrupt screen in very specific case
Caused by ca8f787349dcdf5. This issue is in master actually. Fixing it there
would cause conflicts so won't do that unless needed ;)
Steps to recreate were:
* Split properties editor into two (default startup.blend)
* Move both properties editors to the bottom, so only their headers are visible
* Move the upper edge of the upper properties editor up and down
Although it doesn't happen everytime, you may see the edge between the timeline
and the 3D view move, while the region drawing doesn't update.
What happened is area edge snapping allowed to snap the edge outside of window
bounds (we snap to a 4px grid by default), which screen_vertices_scale
interpreted as window scaling and thus run area size updates.
Diffstat (limited to 'source/blender/editors/space_text/text_header.c')
0 files changed, 0 insertions, 0 deletions