UI: Inconsistencies across animation editors #89626

Closed
opened 2 years ago by tintwotin · 11 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59

Blender Version
Broken: version: 3.0.0 Alpha, branch: soc-2021-vse-strip-thumbnails (modified), commit date: 2021-07-01 12:00, hash: caf2ee76c0
Worked: (newest version of Blender that worked as expected)

Short description of error
{F10210293,size=full}

  • Sidebars aren't same width.
  • Sync Visible Range doesn't take the width of sidebars into account, so with uneven width of sidebars the playhead position will be offset.
  • Graph Editor's playhead doesn't have a line, and no range indication.
  • The VSE has no channel header sidebar.
  • All other editors have no tool bars.
  • The timeline backgrund is different between sequencer and the rest of the editors, including the colors.
  • The VSE has an Overlay drop down, none of the rest of the animation editors have this.
  • Dope sheet highlights the entire channel, other editors don't.
**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59 **Blender Version** Broken: version: 3.0.0 Alpha, branch: soc-2021-vse-strip-thumbnails (modified), commit date: 2021-07-01 12:00, hash: `caf2ee76c0` Worked: (newest version of Blender that worked as expected) **Short description of error** {[F10210293](https://archive.blender.org/developer/F10210293/Unavngivet.png),size=full} - Sidebars aren't same width. - Sync Visible Range doesn't take the width of sidebars into account, so with uneven width of sidebars the playhead position will be offset. - Graph Editor's playhead doesn't have a line, and no range indication. - The VSE has no channel header sidebar. - All other editors have no tool bars. - The timeline backgrund is different between sequencer and the rest of the editors, including the colors. - The VSE has an Overlay drop down, none of the rest of the animation editors have this. - Dope sheet highlights the entire channel, other editors don't.
Poster

Added subscriber: @tintwotin

Added subscriber: @tintwotin
Collaborator

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Collaborator

Graph Editor's playhead doesn't have a line, and no range indication.

That is the Drivers Editor, right? And that one actually should not have a line (at least not tied to time, see D12391: Fix Drivers Editor not hiding vertical part of cursor) and no scrubbing really since the X Axis is not time here (see D12392: Fix Drivers Editor showing playhead on the X Axis)

> Graph Editor's playhead doesn't have a line, and no range indication. That is the Drivers Editor, right? And that one actually should not have a line (at least not tied to time, see [D12391: Fix Drivers Editor not hiding vertical part of cursor](https://archive.blender.org/developer/D12391)) and no scrubbing really since the X Axis is not time here (see [D12392: Fix Drivers Editor showing playhead on the X Axis](https://archive.blender.org/developer/D12392))
Collaborator

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Collaborator

The VSE has an Overlay drop down, none of the rest of the animation editors have this.

What should be in there? (there is nothing drawn as overlays in these editors)

The VSE has no channel header sidebar.

Dont get this one, you are seeing strips (not keyframes/clips)

The timeline backgrund is different between sequencer and the rest of the editors, including the colors.

So you would want to get rid of the alternating rows in the VSE?

Sync Visible Range doesn't take the width of sidebars into account, so with uneven width of sidebars the playhead position will be offset.

Interesting, could be an improvement [but this is really not a bug]

Dope sheet highlights the entire channel, other editors don't.

Graph Editor has no channels, Timeline would be too crowded I assume, VSE has no channels in that sense, NLA highlights its tracks (but of course they look a bit different)
Or is this solely about the Summary?

All other editors have no tool bars.

Also more of a TODO (rather than a bug)

Sidebars aren't same width.

This should be fixed I guess

In any case, will set to Needs Information from User to get above questions out of the way

> The VSE has an Overlay drop down, none of the rest of the animation editors have this. What should be in there? (there is nothing drawn as overlays in these editors) > The VSE has no channel header sidebar. Dont get this one, you are seeing strips (not keyframes/clips) > The timeline backgrund is different between sequencer and the rest of the editors, including the colors. So you would want to get rid of the alternating rows in the VSE? > Sync Visible Range doesn't take the width of sidebars into account, so with uneven width of sidebars the playhead position will be offset. Interesting, could be an improvement [but this is really not a bug] > Dope sheet highlights the entire channel, other editors don't. Graph Editor has no channels, Timeline would be too crowded I assume, VSE has no channels in that sense, NLA highlights its tracks (but of course they look a bit different) Or is this solely about the `Summary`? > All other editors have no tool bars. Also more of a TODO (rather than a bug) > Sidebars aren't same width. This should be fixed I guess In any case, will set to Needs Information from User to get above questions out of the way
Poster

The main point here is that the never-to-be-broken rule of consistency between editors - is broken all the time either for good reasons or for no reason at all - however in a situation where users wants something which will align the VSE with industry standards, but will break consistency it becomes a paramount thing to keep consistency: #89665

Question is how deep the ambition for consistency actually runs. Each and every time a new UI feature serving the 3D View editor is introduced, inconsistency is actually also introduced in all other editors, leaving no plans of implementation in any other editors, when leaving it "finished". I don't see anyone trying to keep consistency across the animation editors or remove the toolbars, the drag'n drop modifiers, the grease pencil, the track headers, the gimbals, the renamer, the python port of ui, the outliner, the filebrowser, the asset browser, or the new sheet editor, just because they're not in consistency with how they're working in all editors. That's pretty inconsistent handling of inconsistency... so how deep does the "consistency" thing actually run?

At some point, I think the BF devs should try to define what "consistency" means and when it should be enforced. Ex. it's pretty obvious that all editors will suffer, if they only can implement features already existing in the other editors. Just imagine the 3D View editor with only features from the Text Editor? Or if all editor workflows should work as if the editing takes place in the 3d space? Most of the time the discussion circles around if a new or changed element is in consistency or not, but never ever about, if it'll give the users the best(better) experience of using an editor/tool/setting, or how to deal with the "industry standard" expectation new users meet the editors of Blender with. In other words, I think it is time the BF address the mantra of "consistency" before it becomes just an unreflected and hollow knee-jerk reaction to everything new or changed.

The main point here is that the never-to-be-broken rule of consistency between editors - is broken all the time either for good reasons or for no reason at all - however in a situation where users wants something which will align the VSE with industry standards, but will break consistency it becomes a paramount thing to keep consistency: #89665 Question is how deep the ambition for consistency actually runs. Each and every time a new UI feature serving the 3D View editor is introduced, inconsistency is actually also introduced in all other editors, leaving no plans of implementation in any other editors, when leaving it "finished". I don't see anyone trying to keep consistency across the animation editors or remove the toolbars, the drag'n drop modifiers, the grease pencil, the track headers, the gimbals, the renamer, the python port of ui, the outliner, the filebrowser, the asset browser, or the new sheet editor, just because they're not in consistency with how they're working in all editors. That's pretty inconsistent handling of inconsistency... so how deep does the "consistency" thing actually run? At some point, I think the BF devs should try to define what "consistency" means and when it should be enforced. Ex. it's pretty obvious that all editors will suffer, if they only can implement features already existing in the other editors. Just imagine the 3D View editor with only features from the Text Editor? Or if all editor workflows should work as if the editing takes place in the 3d space? Most of the time the discussion circles around if a new or changed element is in consistency or not, but never ever about, if it'll give the users the best(better) experience of using an editor/tool/setting, or how to deal with the "industry standard" expectation new users meet the editors of Blender with. In other words, I think it is time the BF address the mantra of "consistency" before it becomes just an unreflected and hollow knee-jerk reaction to everything new or changed.
Collaborator

This is all true to some extend, thx for the input.

My main concern is to not drift into a meta-discussion and stick with actual, practical questions.
I tried to give my view of where consistency makes sense (and where it doesnt), what could be considered as a TODO or as a bug and had some very precise questions (and none of these were answered).
For until this entity of "consistency" is defined in all satisfactory ways, I think we have to decide on a case-by-case basis.
So while I can probably agree to everything you say, I can not derive any information in regards to how to proceed. After all we want to see actions and change the program in some ways, no?

Will stay on Needs Information from User until questions are answered.

This is all true to some extend, thx for the input. My main concern is to not drift into a meta-discussion and stick with actual, practical questions. I tried to give my view of where consistency makes sense (and where it doesnt), what could be considered as a TODO or as a bug and had some very precise questions (and none of these were answered). For until this entity of "consistency" is defined in all satisfactory ways, I think we have to decide on a case-by-case basis. So while I can probably agree to everything you say, I can not derive any information in regards to how to **proceed**. After all we want to see **actions** and **change** the program in some ways, no? Will stay on `Needs Information from User` until questions are answered.
Poster

I'm not the right one to answer those questions, since they're questions revolving around to what extend the BF devs wants to fulfill their rule of consistency across editors. Only they can answer that.

I'm not the right one to answer those questions, since they're questions revolving around to what extend the BF devs wants to fulfill their rule of consistency across editors. Only they can answer that.
Collaborator

Why cant you answer a question like "What should be in a Overlay drop down (when there is nothing drawn as overlays in these editors)?"
After all, you have reported this as a bug.
Wouldnt you agree it makes little sense to have an empty dropdown just for the sake of consistency?

Look, my intention was to save at least these two as things that should (possibly) solved short-term:

  • Sidebars aren't same width
  • possibly coloring of the Summary row
  • possibly Sync Visible Range

But I would kindly ask for your filtering here as well, otherwise I am afraid I would have to close this as a multi-report

Thanks for the report. However to properly track issues we need them to be reported separately.
Please submit a new report for every individual bug.
Why cant you answer a question like "What should be in a Overlay drop down (when there is nothing drawn as overlays in these editors)?" After all, you have reported this as a bug. Wouldnt you agree it makes little sense to have an empty dropdown just for the sake of consistency? Look, my intention was to save at least these two as things that should (possibly) solved short-term: - Sidebars aren't same width - possibly coloring of the Summary row - possibly Sync Visible Range But I would kindly ask for your filtering here as well, otherwise I am afraid I would have to close this as a multi-report ``` Thanks for the report. However to properly track issues we need them to be reported separately. Please submit a new report for every individual bug. ```
Collaborator

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
lichtwerk closed this issue 1 year ago
Collaborator

Thanks for the report. However to properly track issues we need them to be reported separately.

Please submit a new report for every individual bug.

Thanks for the report. However to properly track issues we need them to be reported separately. Please submit a new report for every individual bug.
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#89626
Loading…
There is no content yet.