diff options
Diffstat (limited to 'doc/python_api/examples/bpy.types.Menu.py')
| -rw-r--r-- | doc/python_api/examples/bpy.types.Menu.py | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/python_api/examples/bpy.types.Menu.py b/doc/python_api/examples/bpy.types.Menu.py index 4ca18a67b78..c2162444055 100644 --- a/doc/python_api/examples/bpy.types.Menu.py +++ b/doc/python_api/examples/bpy.types.Menu.py @@ -1,21 +1,21 @@ """ Basic Menu Example ++++++++++++++++++ -This script is a simple menu, menus differ from panels in that they must + +Here is an example of a simple menu. Menus differ from panels in that they must reference from a header, panel or another menu. -Notice the 'CATEGORY_MT_name' :class:`Menu.bl_idname`, this is a naming +Notice the 'CATEGORY_MT_name' in :class:`Menu.bl_idname`, this is a naming convention for menus. .. note:: - Menu subclasses must be registered before referencing them from blender. .. note:: - Menu's have their :class:`Layout.operator_context` initialized as - 'EXEC_REGION_WIN' rather then 'INVOKE_DEFAULT', so if the operator context - needs to initialize inputs from the :class:`Operator.invoke` function - then this needs to be explicitly set. + Menus have their :class:`Layout.operator_context` initialized as + 'EXEC_REGION_WIN' rather than 'INVOKE_DEFAULT' (see :ref:`Execution Context <operator-execution_context>`). + If the operator context needs to initialize inputs from the + :class:`Operator.invoke` function, then this needs to be explicitly set. """ import bpy |