archive/blender-archive
Archived
1
1
Fork 0
Code Pull Requests Packages Activity

Cleanup: operator execution types didn't read well on one line

Browse Source
This commit is contained in:
Campbell Barton
2020-10-09 12:14:22 +11:00
parent afc090f339
commit decb3b10aa
1 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
doc/python_api/examples/bpy.ops.2.py
View File

@@ -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 This determines the context that is given for the operator to run in, and whether
invoke() is called or only execute(). invoke() is called or only execute().
'EXEC_DEFAULT' is used by default, running only the execute() method, but you may ``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 want the operator to take user interaction with ``INVOKE_DEFAULT`` which will also
call invoke() if existing. call invoke() if existing.
The execution context is one of: The execution context is one of:
('INVOKE_DEFAULT', 'INVOKE_REGION_WIN', 'INVOKE_REGION_CHANNELS',
'INVOKE_REGION_PREVIEW', 'INVOKE_AREA', 'INVOKE_SCREEN', 'EXEC_DEFAULT', - ``INVOKE_DEFAULT``
'EXEC_REGION_WIN', 'EXEC_REGION_CHANNELS', 'EXEC_REGION_PREVIEW', 'EXEC_AREA', - ``INVOKE_REGION_WIN``
'EXEC_SCREEN') - ``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 # collection add popup