bpy.props operator example misses property access #54286
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#54286
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Operator Example for using properties in an operator shows this code:
This code has two downsides.
I would suggest something like:
This actually shows how to use the properties in the code, and doesn't block the UI. A nice touch would be to add an explanation that the properties are also shown in the redo panel in the 3D view.
Note that I also changed the
bl_idname
, as this is an example about properties, not about dialogue boxes, and changed the class name to use the standard operator naming convention.Added subscriber: @dr.sybren
Added subscriber: @VukGardasevic
I agree since the example with invoking a pop-up is already mentioned here on the Operator page.
The bpy.props page can include a link to it, where the three possibilities related to operator drawing / accessing properties can be explained in more depth, possibly including a notice about some drawbacks of each approach.
This issue was referenced by blender/blender@b76471c1f9
Changed status from 'Open' to: 'Resolved'