From eb89308019501482119d12a0b4542fadb0cde2fa Mon Sep 17 00:00:00 2001 From: Dion Moult Date: Fri, 2 Jul 2021 19:16:55 +1000 Subject: [PATCH] Minor fix --- src/blenderbim/docs/blenderbim/undo_system.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/blenderbim/docs/blenderbim/undo_system.rst b/src/blenderbim/docs/blenderbim/undo_system.rst index 1bc389b384..ddf7f1b717 100644 --- a/src/blenderbim/docs/blenderbim/undo_system.rst +++ b/src/blenderbim/docs/blenderbim/undo_system.rst @@ -51,7 +51,7 @@ This scenario where there is pure IfcOpenShell never occurs with the BlenderBIM Add-on. Instead, stuff happens in Blender operators. .. code-block:: python - :emphasize-lines: 5,7,8,10,13 + :emphasize-lines: 6,7 class Foobar(bpy.types.Operator): bl_idname = "foobar" @@ -63,7 +63,6 @@ Add-on. Instead, stuff happens in Blender operators. def _execute(self, context): ifcopenshell.api.run("foo.bar", IfcStore.get_file()) - context.scene.name = "Foobar" return {"FINISHED"} When your operator manipulates (creates, removes, or edits) IFC data directly or