PME working habits

This older guide has been reduced to the advice that remains broadly useful. The linked pages contain the maintained instructions and their source conversations.

General reminders

• Name a menu after the job it supports, not after the PME feature used to build it.
• Keep the first menu small. Remove entries you never reach for.
• Choose the narrowest practical keymap scope, then test in the editor and mode where you will actually work.
• When code fails, check editor, region, mode, selection, active object, and operator context before adding workarounds.
• Export and preserve PME data before a migration or a large reorganization.

Continue with a practical guide

• Build your first useful Pie Menu
• Borrow a workflow design from selected examples
• Use PME command, Custom, Poll, Property, and external-script patterns
• Run a Macro from another PME item
• Find PME definitions, resources, and backups
• Restore menus from an automatic backup
• Start troubleshooting from the symptom

For product-level behavior and installation, use the current PME documentation.