From decb3b10aadc312aac8c15c66deb4f9f1822ab11 Mon Sep 17 00:00:00 2001 From: Campbell Barton Date: Fri, 9 Oct 2020 12:14:22 +1100 Subject: Cleanup: operator execution types didn't read well on one line --- doc/python_api/examples/bpy.ops.2.py | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) (limited to 'doc/python_api') diff --git a/doc/python_api/examples/bpy.ops.2.py b/doc/python_api/examples/bpy.ops.2.py index 5f98c8a6656..d8ddb848669 100644 --- a/doc/python_api/examples/bpy.ops.2.py +++ b/doc/python_api/examples/bpy.ops.2.py @@ -9,15 +9,24 @@ When calling an operator you may want to pass the execution context. This determines the context that is given for the operator to run in, and whether invoke() is called or only execute(). -'EXEC_DEFAULT' is used by default, running only the execute() method, but you may -want the operator to take user interaction with 'INVOKE_DEFAULT' which will also +``EXEC_DEFAULT`` is used by default, running only the ``execute()`` method, but you may +want the operator to take user interaction with ``INVOKE_DEFAULT`` which will also call invoke() if existing. The execution context is one of: -('INVOKE_DEFAULT', 'INVOKE_REGION_WIN', 'INVOKE_REGION_CHANNELS', -'INVOKE_REGION_PREVIEW', 'INVOKE_AREA', 'INVOKE_SCREEN', 'EXEC_DEFAULT', -'EXEC_REGION_WIN', 'EXEC_REGION_CHANNELS', 'EXEC_REGION_PREVIEW', 'EXEC_AREA', -'EXEC_SCREEN') + +- ``INVOKE_DEFAULT`` +- ``INVOKE_REGION_WIN`` +- ``INVOKE_REGION_CHANNELS`` +- ``INVOKE_REGION_PREVIEW`` +- ``INVOKE_AREA`` +- ``INVOKE_SCREEN`` +- ``EXEC_DEFAULT`` +- ``EXEC_REGION_WIN`` +- ``EXEC_REGION_CHANNELS`` +- ``EXEC_REGION_PREVIEW`` +- ``EXEC_AREA`` +- ``EXEC_SCREEN`` """ # collection add popup -- cgit v1.2.3