UI Experiment: Operator Preferences on Status Bar #126477
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#126477
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Harley/blender:OpPrefs"
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?
Less a proposal and more a thing to talk about. Once applied while
navigating in viewport this shows options to change related user
preferences. The idea of making the preferences available where used.
No need for users to know what things can be changed.
While orbiting:
While zooming:
While panning:
As agreed on during the latest module meeting. It'd be good to move forward with this since it exposes certain settings that many users seem to expect when coming from other software.
Another popular ones:
Auto Depth
(shortcutD
), which should show up during orbit, panning, and zoom:Zoom to Position
(shortcutZ
), should show up during zoom. Ctrl+MMB only, I'm not sure we can update the statusbar during scroll, can we?One weird complication is that I was unable to differentiate between orbiting, panning, and zooming. It was all treated like one transform operation so I couldn't show the correct options at the correct times. I'll take another look in a bit though.
It seems good to reveal these half-hidden options in the status bar itself!
The settings supported by the operator should be found in
ViewOpsType::flag
.The way each of these configurations is initiated is in
ViewOpsData::init_navigation(...)
@ -529,0 +540,4 @@
if (event->type == EVT_PKEY) {
vod->viewops_flag ^= VIEWOPS_FLAG_PERSP_ENSURE;
U.uiflag ^= USER_AUTOPERSP;
U.runtime.is_dirty = true;
Changes to
vod->viewops_flag
here seem to be OK, but I think changes toU.uiflag
should only be made upon operator confirmation.If the user cancels navigation,
U.uiflag
would not need to be reverted in that case.@ -598,0 +620,4 @@
status.opmodal(IFACE_("Move"), op->type, VIEWROT_MODAL_SWITCH_MOVE);
status.opmodal(IFACE_("Rotate"), op->type, VIEWROT_MODAL_SWITCH_ROTATE);
if (vod->nav_type == &ViewOpsType_rotate) {
To check if the operator supports any of these settings, you could check the
vod->nav_type->flag
and the flagsVIEWOPS_FLAG_ORBIT_SELECT
andVIEWOPS_FLAG_PERSP_ENSURE
.Oh, that is the trick. I didn't actually notice that
vod->nav_type->flag
was different thanvod->viewops_flag
for some reason. Makes perfect sense and works now.Now to ponder it and see if it is a useful idea...
@pablovazquez
With help from @mano-wii this might be working as intended. Seems to work. It is a little awkward to change these options while doing an operation that requires ctrl or shift, but doable. And probably not something that is changed often since now buried in Preferences.
Although these settings changes affect the NEXT use of the operation, that doesn't seem to be an issue and feels like expected behavior. Or I could be wrong and this would result in bug reports about it not having immediate effect.
@pablovazquez
I added even more options, very likely more than we'd want, like turntable/trackball, invert, horizontal zoom, etc. Just so this can help us in judging this idea and how far we'd go with it.
I remembered that some other options that affect navigation are in the Sidebar.
They are the Lock options and override the options in the preferences:
I find this a bit confusing, as these options are similar, mutually exclusive and spread out in different places.
I made a mockup (using Paint) of something that I think could be a better and more visible for navigation operations:
@JulianEisel - I added a separating bar and "Preferences: " (along with the Preferences icon) to see how this feels.
It still feels okay. Without the icon I found it hard to see the differences in the sections well.
I think this latest change makes things quite clear now visually. I don't have a strong opinion about the feature itself, but if we add it, I think version is quite fine.
Checkout
From your project repository, check out a new branch and test the changes.