flag look different in dynotopo (trivial cosmetic problem) #49402

Closed
opened 2016-09-19 16:43:08 +02:00 by blend-it · 5 comments
Member

System Information
NA

Blender Version
2.78 RC2

Short description of error
only appearance problem.
flag to toggle Dynotopo (sculpt mode) in tool shelf looks different than any other flag in toolshelf and property (see img)
flag.PNG

**System Information** NA **Blender Version** 2.78 RC2 **Short description of error** only appearance problem. flag to toggle Dynotopo (sculpt mode) in tool shelf looks different than any other flag in toolshelf and property (see img) ![flag.PNG](https://archive.blender.org/developer/F363101/flag.PNG)
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @blend-it

Added subscriber: @blend-it
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Julian Eisel self-assigned this 2016-09-19 17:33:41 +02:00
Member

Thing is that usually these buttons just represent a boolean property, but in the dyntopo case we need to use an operator button (we have to do quite some additional stuff when enabling dyntopo). I can't see any way to get this working nicely without bigger changes or hacks (using RNA property set callback wouldn't work as we need bContext access for enabling dyntopo, update callback could work but would be quite a hack).

So thanks for the report but closing for now. Will try to think of a better way to fix this and consider it during future refactors/rewrites.

Thing is that usually these buttons just represent a boolean property, but in the dyntopo case we need to use an operator button (we have to do quite some additional stuff when enabling dyntopo). I can't see any way to get this working nicely without bigger changes or hacks (using RNA property `set` callback wouldn't work as we need `bContext` access for enabling dyntopo, update callback could work but would be quite a hack). So thanks for the report but closing for now. Will try to think of a better way to fix this and consider it during future refactors/rewrites.
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#49402
No description provided.