Move tool settings bar to editors #63516

Closed
opened 2019-04-12 08:23:09 +02:00 by Brecht Van Lommel · 15 comments

Move tool settings bar from top bar to individual editors with toolbar.

  • 3D Viewport
  • UV editor
  • Movie Clip editor
  • Node editor?

The tool settings bar visibility will be opaque and above the header. It will be possible to hide just the tool settings but keep the header. In this case the editor type switching moves from the tool settings bar to the header.

The tool settings bar would contain:

  • Editor type switching
  • Mode and select mode
  • Tool settings
  • Orientation, snap, ..
  • Popovers for mode panels

The header would contain

  • Menus
  • Display settings

Ideally quad splitting would be improved so it's easy to have e.g. two viewports with a single topbar, but this is not required for 2.80.

Move tool settings bar from top bar to individual editors with toolbar. * 3D Viewport * UV editor * Movie Clip editor * Node editor? The tool settings bar visibility will be opaque and above the header. It will be possible to hide just the tool settings but keep the header. In this case the editor type switching moves from the tool settings bar to the header. The tool settings bar would contain: * Editor type switching * Mode and select mode * Tool settings * Orientation, snap, .. * Popovers for mode panels The header would contain * Menus * Display settings Ideally quad splitting would be improved so it's easy to have e.g. two viewports with a single topbar, but this is not required for 2.80.
Author
Owner

Added subscriber: @brecht

Added subscriber: @brecht

Added subscriber: @LucianoMunoz

Added subscriber: @LucianoMunoz

Added subscriber: @lsscpp

Added subscriber: @lsscpp

This comment was removed by @lsscpp

*This comment was removed by @lsscpp*

Added subscriber: @Rickyx

Added subscriber: @Rickyx
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar

Added subscriber: @Znio.G

Added subscriber: @Znio.G

i would like to point out that moving "Mode and select mode..etc" to the tool settings bar is not ideal and here is why.

  1. we will not be able to fit all tool settings in one row. ..it's doable now even if we split the viewport into 2 or more, we will lose that if more options are added.
  2. each tool in each mode has it's special menus that some are only activated by their sub-components, so these menus work best near their modes as it is now and some have quite few like the grease pencil edit mode, should they move too to the tool settings bar which doesn't have any space left and therefore causes the header to be empty while toolbar cluttered?.
  3. generally users use pie menu for switching modes and hotkeys for their components, keeping this in the header not only gives a visual clearity between the two but gives freedom to hide the header as options there are secondary to the tool settings which are used more often than them so the tool bar stay open while header can be switched off with a hotkey or quick favorites.

this is my two cents that i think makes sense at least to me, other parts i have no objection as they don't interfere that much.
1.jpg

i would like to point out that moving "Mode and select mode..etc" to the tool settings bar is not ideal and here is why. 1. we will not be able to fit all tool settings in one row. ..it's doable now even if we split the viewport into 2 or more, we will lose that if more options are added. 2. each tool in each mode has it's special menus that some are only activated by their sub-components, so these menus work best near their modes as it is now and some have quite few like the grease pencil edit mode, should they move too to the tool settings bar which doesn't have any space left and therefore causes the header to be empty while toolbar cluttered?. 3. generally users use pie menu for switching modes and hotkeys for their components, keeping this in the header not only gives a visual clearity between the two but gives freedom to hide the header as options there are secondary to the tool settings which are used more often than them so the tool bar stay open while header can be switched off with a hotkey or quick favorites. this is my two cents that i think makes sense at least to me, other parts i have no objection as they don't interfere that much. ![1.jpg](https://archive.blender.org/developer/F6963076/1.jpg)
Member

Added subscriber: @jendrzych

Added subscriber: @jendrzych
Campbell Barton was assigned by Brecht Van Lommel 2019-04-28 12:17:08 +02:00

Added subscribers: @WilliamReynish, @pablovazquez

Added subscribers: @WilliamReynish, @pablovazquez

This is done apart from Mode and select mode being in the header currently (a minor change).

Since this issue was created we had a design discussion with @pablovazquez & @brecht where we agreed on D4721, pending feedback from @billreynish.

It's not clear which parts of this task still need to be worked on.
Probably we'll sort this out in a UI design meeting instead.

This is done apart from `Mode and select mode` being in the header currently (a minor change). Since this issue was created we had a design discussion with @pablovazquez & @brecht where we agreed on [D4721](https://archive.blender.org/developer/D4721), pending feedback from @billreynish. It's not clear which parts of this task still need to be worked on. Probably we'll sort this out in a UI design meeting instead.

Added subscriber: @AlbertoVelazquez

Added subscriber: @AlbertoVelazquez

I want to remember this problem that blender actually have if the user move the N-shelf to the left. The panel is place at right of T-shelf, making hard to use it.

image.png

I don't know a perfect solution, The first idea is move to the left. Also a transparent BG could work with few tabs. ut this list will grow easily

I want to remember this problem that blender actually have if the user move the N-shelf to the left. The panel is place at right of T-shelf, making hard to use it. ![image.png](https://archive.blender.org/developer/F6994741/image.png) I don't know a perfect solution, The first idea is move to the left. Also a transparent BG could work with few tabs. ut this list will grow easily
Author
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author
Owner

The original task is finished now.

The original task is finished now.
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
9 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#63516
No description provided.