Reference Guide

Find the references you need to configure PME menus and write code.

Some existing references describe older versions. Inclusion here does not mean every linked procedure has been verified in PME 2.1. Check each page’s target version and constraints; where the scope is unspecified, verify it in your environment.

Menus and operations

Menu type selection in a Blender 5.1.0 / PME 2.1.0-beta.6 development environment.

Start with Common Editor Elements for the editor interface and slots. References for individual menus are listed below.

Topic	Reference
Vector Menu	Vector Menu Editor
Floating Panel	Floating Panel Editor
Property Stack	Property Stack Editor
Context Router	Context Router Editor
Pie Menu	Pie Menu Editor
Regular Menu	Regular Menu Editor
Pop-up Dialog	Pop-up Dialog Editor
Stack Key	Stack Key Editor
Sticky Key	Sticky Key Editor
Macro Operator	Macro Operator Editor
Modal Operator	Modal Operator Editor
Property	Property Editor
Sidebar layout	Side Panel Editor
Hiding existing panels	Hiding Unused Panels

This is a list of existing references, not an exhaustive list of PME menu types.

Invocation conditions and Blender UI

• Choosing a Keymap: selecting the Keymap for the place you work.

• Poll Method: conditions that make a menu available.

• Interactive Panels and Extend Panel: capturing and extending existing UI.

• Capture Menu: capture Blender operations or properties and add them to PME menus.

• Custom Icons: icon configuration.

Code, APIs, and storage

• Writing and Running Code: input format, variables, external files, execution requirements, and errors.

• Code Examples: configurations and code for specific tasks.

• API Reference: PME functions, variables, and arguments.

• Public API: using PME from external scripts.

• Boot Options: startup settings and import pme.

• Settings: PME preferences.

• File Locations: settings and user files.

• Glossary: Blender and PME terminology.

Reference videos

• Original Author’s Videos: videos from roaoao’s channel grouped by feature.

What to tell an AI assistant

Along with the desired result, provide the following information to help establish the requirements. If you do not know a value, ask how to check it instead of guessing.

• Your PME and Blender versions.

• The menu type and field being configured, and any existing code.

• The editor, mode, target objects, and selection state.

• The expected result; if something fails, the actual result and error message.

Ask the AI to include its source pages, prerequisites, the field to configure, and how to verify the result. If the references do not settle a question, the AI should identify the target version and unverified details, then ask for the missing information or point to further sources. It should build instructions from verified APIs rather than assume an unconfirmed API is available.

Search PME Treasure for earlier questions, answers, and examples.