Discrepancy between bpy.ops.object.mode_set() and bpy.context.mode #79122

Closed
opened 2020-07-20 18:11:45 +02:00 by Sam Van Hulle · 5 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67

Blender Version
Broken: version: 2.83.2, branch: master, commit date: 2020-07-09 05:50, hash: 239fbf7d93

Short description of error
Some of bpy.context.mode's values differ from bpy.ops.object.mode_set(mode)'s.
Not sure if this is intentional. I can see why the operator only needs a single enum value for Edit Mode, but the discrepancy between them concerning painting and particle modes is just annoying.

bpy.context.mode bpy.ops.object.mode_set(mode)
EDIT_MESH EDIT
EDIT_CURVE EDIT
EDIT_SURFACE EDIT
EDIT_TEXT EDIT
EDIT_ARMATURE EDIT
EDIT_METABALL EDIT
EDIT_LATTICE EDIT
PAINT_WEIGHT WEIGHT_PAINT
PAINT_VERTEX VERTEX_PAINT
PAINT_TEXTURE TEXTURE_PAINT
PARTICLE PARTICLE_EDIT
**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67 **Blender Version** Broken: version: 2.83.2, branch: master, commit date: 2020-07-09 05:50, hash: `239fbf7d93` **Short description of error** Some of `bpy.context.mode`'s values differ from `bpy.ops.object.mode_set(mode)`'s. Not sure if this is intentional. I can see why the operator only needs a single enum value for Edit Mode, but the discrepancy between them concerning painting and particle modes is just annoying. | **`bpy.context.mode`** | **`bpy.ops.object.mode_set(mode)`** | | -- | -- | | EDIT_MESH | EDIT | | EDIT_CURVE | EDIT | | EDIT_SURFACE | EDIT | | EDIT_TEXT | EDIT | | EDIT_ARMATURE | EDIT | | EDIT_METABALL | EDIT | | EDIT_LATTICE | EDIT | | PAINT_WEIGHT | WEIGHT_PAINT | | PAINT_VERTEX | VERTEX_PAINT | | PAINT_TEXTURE | TEXTURE_PAINT | | PARTICLE | PARTICLE_EDIT |
Author

Added subscriber: @frameshift

Added subscriber: @frameshift

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Richard Antalik self-assigned this 2020-07-22 07:02:55 +02:00

I don't think this is intentional, as in we want to use different strings on purpose. But this definitely isn't a bug.

Changing this probably isn't very hard, however there are implications that have to be considered, for example a lot of addons may stop working after this change.

I don't think this is intentional, as in we want to use different strings on purpose. But this definitely isn't a bug. Changing this probably isn't very hard, however there are implications that have to be considered, for example a lot of addons may stop working after this change.
Author

In #79122#983270, @iss wrote:
I don't think this is intentional, as in we want to use different strings on purpose. But this definitely isn't a bug.

Changing this probably isn't very hard, however there are implications that have to be considered, for example a lot of addons may stop working after this change.

... like with most Python API changes? ;)
To me this just looks like an oversight. And I'd personally rather see addons updating their code according to an API change, than having to keep remapping these strings for all eternity because of something that wasn't intentional to begin with.

original_mode = bpy.context.mode
context_mode_remap = {
    'EDIT_MESH': 'EDIT',
    'PAINT_WEIGHT': 'WEIGHT_PAINT',
    'PAINT_VERTEX': 'VERTEX_PAINT',
    'PAINT_TEXTURE': 'TEXTURE_PAINT'
}
if context_mode_remap.get(original_mode):
    original_mode = context_mode_remap[original_mode]
bpy.ops.object.mode_set(mode=original_mode)

Anyway. It's a small thing, I just thought it was worth pointing out.

> In #79122#983270, @iss wrote: > I don't think this is intentional, as in we want to use different strings on purpose. But this definitely isn't a bug. > > Changing this probably isn't very hard, however there are implications that have to be considered, for example a lot of addons may stop working after this change. ... like with most Python API changes? ;) To me this just looks like an oversight. And I'd personally rather see addons updating their code according to an API change, than having to keep remapping these strings for all eternity because of something that wasn't intentional to begin with. ``` original_mode = bpy.context.mode context_mode_remap = { 'EDIT_MESH': 'EDIT', 'PAINT_WEIGHT': 'WEIGHT_PAINT', 'PAINT_VERTEX': 'VERTEX_PAINT', 'PAINT_TEXTURE': 'TEXTURE_PAINT' } ``` ``` if context_mode_remap.get(original_mode): original_mode = context_mode_remap[original_mode] bpy.ops.object.mode_set(mode=original_mode) ``` Anyway. It's a small thing, I just thought it was worth pointing out.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info 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
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#79122
No description provided.