Page MenuHome

Fix T62325: Selecting preset does not trigger redraw
Needs RevisionPublic

Authored by Jacques Lucke (JacquesLucke) on Mar 7 2019, 6:27 PM.



Just not sure if there is a deeper issue that makes it not-redraw automatically
in this case.

Diff Detail

rB Blender
presets-update (branched from master)
Build Status
Buildable 3077
Build 3077: arc lint + arc unit

Event Timeline

Brecht Van Lommel (brecht) requested changes to this revision.EditedMar 7 2019, 7:29 PM

There's a deeper issue here. Normally setting a property value through Python will trigger the required redraw.

Running e.g. C.scene.cycles.samples = 999 in the console seems to not redraw as well. We should find out which commit broke that.

This revision now requires changes to proceed.Mar 7 2019, 7:29 PM

Found the first issue. Unfortunately, it is still not the root cause of the issue.
This commit changed the redraw behavior when a preset is changed: rB5ec1d709e7717.

bpy.ops.script.python_file_run called ED_region_tag_redraw internally.

Unfortunately, C.scene.cycles.samples = 999 still does not trigger a redraw before commit.

Actually, running this script in Blender 2.79 does not redraw the properties panel as well. (running it in the console, redraws though)

So I guess, this never worked. I do not know why it should work tbh, does Blender keep track of where specific properties are drawn in the UI?

The actual bug here seems to be that executing a statement in the console does not trigger a full redraw anymore (trying to find where this happens in Blender 2.7 currently).