Ticking the "Manipulator" check box OFF in the Preferences > Interface menu does not get respected in subsequent Blender sessions #48112

Closed
opened 2016-04-11 19:48:56 +02:00 by Chris Offner · 7 comments

System Information
Windows 10

Blender Version
Broken: 2.77a

When I tick OFF the "Manipulator" check box in the User Preferences > Interface menu and Save User Preferences, the manipulator will be on again when launching Blender the next time

Exact steps for others to reproduce the error

  • Open User Preferences
  • In the Interface tab, untick the Manipulator check box, observe the manipulator get deactivated in the 3D view
  • Click on Save User Settings
  • Quit and restart Blender
  • Observe that upon restarting, Blender has the manipulator active again in the 3D viewport
  • Open User Preferences again, observe that the Manipulator checkbox is indeed ticked still unticked
  • Tick and untick the check box to deactivate the manipulator again. The change will not carry over to the next session though
**System Information** Windows 10 **Blender Version** Broken: 2.77a **When I tick OFF the "Manipulator" check box in the User Preferences > Interface menu and Save User Preferences, the manipulator will be on again when launching Blender the next time** **Exact steps for others to reproduce the error** - Open **User Preferences** - In the *Interface* tab, untick the **Manipulator** check box, observe the manipulator get *deactivated* in the 3D view - Click on **Save User Settings** - Quit and restart Blender - Observe that upon restarting, Blender has the manipulator *active* again in the 3D viewport - Open **User Preferences** again, observe that the **Manipulator** checkbox is indeed ticked still unticked - Tick and untick the check box to *deactivate* the manipulator again. The change will not carry over to the next session though
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @chrisoffner3d

Added subscriber: @chrisoffner3d

Added subscriber: @Sergey

Added subscriber: @Sergey

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2016-04-12 10:41:25 +02:00

Thanks for the report, but it's just a limitation of current user preferences system. Basically, each 3d viewport has own setting to control visibility of manipulator. When you're toggling "Manipulator" in user preferences it iterates over all existing viewports and updates manipulator setting there.

Now, when you save user preferences it only includes that option, it does not include state of existing viewports. This makes it so manipulator flag from default startup is stll used after re-opening blender and user preference is only used for newly opened 3d viewport editors.

In order to solve your particular case, also save the startup file.

Listing the limitation there: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/UserInterface#User_Preferences

Thanks for the report, but it's just a limitation of current user preferences system. Basically, each 3d viewport has own setting to control visibility of manipulator. When you're toggling "Manipulator" in user preferences it iterates over all existing viewports and updates manipulator setting there. Now, when you save user preferences it only includes that option, it does not include state of existing viewports. This makes it so manipulator flag from default startup is stll used after re-opening blender and user preference is only used for newly opened 3d viewport editors. In order to solve your particular case, also save the startup file. Listing the limitation there: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/UserInterface#User_Preferences
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Going through old UI ToDo tasks - Parts relating to this were reworked entirely during 2.8. After a quick test, what's reported here doesn't seem to be an issue anymore. So marking the ToDo item as done.

Going through old UI ToDo tasks - Parts relating to this were reworked entirely during 2.8. After a quick test, what's reported here doesn't seem to be an issue anymore. So marking the ToDo item as done.
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
3 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#48112
No description provided.