Graph Editor - Box select and transform keys issue #64106

Closed
opened 4 years ago by Oskar3d · 9 comments

System Information
Operating system: Windows
Graphics card: GTX660ti

Blender Version
Broken: 2.80, b331515d2e, 2019-05-02 17:03

Short description of error
When you select keys using the box select and transform the keys they behave in a strange way. (see the GIFs below)
Seems like the key handles are not affected by the selection.

In general I think the key/point should be treated as the parent of its handles. And when the key is moved the handles should follow it, no matter if they are selected or not.

If you select a key by just clicking on it it works as expected.

Exact steps for others to reproduce the error

  • Create a few keys for an object in the Graph Editor.
  • Box select a key and move it.

Blender:
blender_graph.gif

Maya:
maya_graph.gif

After Effects
after_effects_graph.gif

Inkscape:
inkscape_graph.gif

**System Information** Operating system: Windows Graphics card: GTX660ti **Blender Version** Broken: 2.80, b331515d2e47, 2019-05-02 17:03 **Short description of error** When you select keys using the box select and transform the keys they behave in a strange way. (see the GIFs below) Seems like the key handles are not affected by the selection. In general I think the key/point should be treated as the parent of its handles. And when the key is moved the handles should follow it, no matter if they are selected or not. If you select a key by just clicking on it it works as expected. **Exact steps for others to reproduce the error** * Create a few keys for an object in the Graph Editor. * Box select a key and move it. Blender: ![blender_graph.gif](https://archive.blender.org/developer/F7003257/blender_graph.gif) Maya: ![maya_graph.gif](https://archive.blender.org/developer/F7003256/maya_graph.gif) After Effects ![after_effects_graph.gif](https://archive.blender.org/developer/F7003255/after_effects_graph.gif) Inkscape: ![inkscape_graph.gif](https://archive.blender.org/developer/F7003258/inkscape_graph.gif)
Poster

Added subscriber: @Oskar3d

Added subscriber: @Oskar3d

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

I can confirm this, but it is partially my fault in the Industry Compatible Keymap, which I know you are using. I have the operator set to

 "include_handles", True

If I set to

 "include_handles", False

It also selects the handles automatically, and they will move correctly.

However, I still think this is a bug, but something we can work around in the keymap.

I can confirm this, but it is partially my fault in the Industry Compatible Keymap, which I know you are using. I have the operator set to ``` "include_handles", True ``` If I set to ``` "include_handles", False ``` It also selects the handles automatically, and they will move correctly. However, I still think this is a bug, but something we can work around in the keymap.

I fixed the keymap, but will leave this ticket as confirmed, because I think this is still a bug, albeit an obscure one since the default keymaps work around it.

I fixed the keymap, but will leave this ticket as confirmed, because I think this is still a bug, albeit an obscure one since the default keymaps work around it.
ideasman42 was assigned by WilliamReynish 4 years ago

Added subscriber: @ideasman42

Added subscriber: @ideasman42

@ideasman42: feel free to re-assign if this is not for you.

Note: to reproduce the issue, you must change the keymap so box select in the graph editor is set to include handles = true.

@ideasman42: feel free to re-assign if this is not for you. Note: to reproduce the issue, you must change the keymap so box select in the graph editor is set to include handles = true.
Collaborator

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Collaborator

Closing for the same reason as #70459: Stricktly speaking, it's not a bug, but a design issue. We're trying to address this with #70634.
But thanks nevertheless, helps justifying the changes :)

Closing for the same reason as #70459: Stricktly speaking, it's not a bug, but a design issue. We're trying to address this with #70634. But thanks nevertheless, helps justifying the changes :)
Collaborator

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
JulianEisel closed this issue 3 years ago
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
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

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