GPencil: Add more controls and side panel to Dopesheet #72026

Closed
opened 2019-11-28 20:45:57 +01:00 by Antonio Vazquez · 5 comments

Actually, the dopesheet needs more icons and a side panel to handle layers without using the properties panel that can be used for other tasks as Vertex Colors.

This has been a long requested feature by artists.

This is the change we have been testing.

DopeSheet.png

Changes:

  • Add new Opacity slider.
  • Add Blend icon.
  • Add Onion icon.
  • Add Buttons in header for moving up/down and create/delete layers.
  • Side panel with all layer properties.

As the number of buttons are limited by Dopesheet core design and we cannot change it, I have used slider section to display all new controls. Also, the show sliders option was set to true by default in 2D template.

Note: I have done and tested all changes in greasepencil-object branch before.

Actually, the dopesheet needs more icons and a side panel to handle layers without using the properties panel that can be used for other tasks as Vertex Colors. This has been a long requested feature by artists. This is the change we have been testing. ![DopeSheet.png](https://archive.blender.org/developer/F8175873/DopeSheet.png) Changes: * Add new Opacity slider. * Add Blend icon. * Add Onion icon. * Add Buttons in header for moving up/down and create/delete layers. * Side panel with all layer properties. As the number of buttons are limited by Dopesheet core design and we cannot change it, I have used slider section to display all new controls. Also, the `show sliders` option was set to `true` by default in 2D template. Note: I have done and tested all changes in `greasepencil-object` branch before.
Antonio Vazquez self-assigned this 2019-11-28 20:45:57 +01:00
Author
Member
Added subscribers: @antoniov, @mendio, @pepe-school-land, @WilliamReynish
Author
Member

See D6328

See [D6328](https://archive.blender.org/developer/D6328)
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

This adds quite some complexity to the channel list, that I'm not too keen about having.
It is not something that scales well. Currently there are 3 options that we consider useful enough to be there. It's not unlikely that in future we'll find more options to be put there too.

Were other solutions considered? For example the toggles could be placed in the context menu instead, which means there's no need to go to a sidebar at all. We already have options like keyframe type, handle type or interpolation mode there, so it would make sense to have the blend type there too, for example.
A different way of changing the layer opacity could be with Shift+F, which would bring up a radial control. So it would work just like the strength shortcut in paint modes.

I am aware that we use a similar slider to the layer opacity for shape keys and meshes, but maybe it's a good idea to reevaluate these too. I'm not that keen on them either.


I don't want to sound too negative, and I'm not totally against the changes here. But I'd like to see a good rationale for the chosen design, which isn't given.

This adds quite some complexity to the channel list, that I'm not too keen about having. It is not something that scales well. Currently there are 3 options that we consider useful enough to be there. It's not unlikely that in future we'll find more options to be put there too. Were other solutions considered? For example the toggles could be placed in the context menu instead, which means there's no need to go to a sidebar at all. We already have options like keyframe type, handle type or interpolation mode there, so it would make sense to have the blend type there too, for example. A different way of changing the layer opacity could be with Shift+F, which would bring up a radial control. So it would work just like the strength shortcut in paint modes. I am aware that we use a similar slider to the layer opacity for shape keys and meshes, but maybe it's a good idea to reevaluate these too. I'm not that keen on them either. --- I don't want to sound too negative, and I'm not totally against the changes here. But I'd like to see a good rationale for the chosen design, which isn't given.
Author
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
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#72026
No description provided.