First selected object in Outliner is active one, while it is the last selected one that becomes active in 3DView #69505

Closed
opened 2019-09-04 21:52:32 +02:00 by Fouad Hafiz · 14 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02

Blender Version
Broken: version: 2.81 (sub 5), branch: master, commit date: 2019-09-03 16:04, hash: b3b59e3b56
Worked: (optional)

Short description of error
The parenting behavior is backwards in the outliner. When parenting objects in the outliner, the active object becomes the child instead of the parent.

Exact steps for others to reproduce the error

Create two objects and attempt to create a parent relationship using CTRL+P

[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02 **Blender Version** Broken: version: 2.81 (sub 5), branch: master, commit date: 2019-09-03 16:04, hash: `b3b59e3b56` Worked: (optional) **Short description of error** The parenting behavior is backwards in the outliner. When parenting objects in the outliner, the active object becomes the child instead of the parent. **Exact steps for others to reproduce the error** Create two objects and attempt to create a parent relationship using CTRL+P [Based on the default startup or an attached .blend file (as simple as possible)]
Author

Added subscriber: @foodi-4

Added subscriber: @foodi-4
Fouad Hafiz changed title from Parneting behaviour is backwards in the outliner to Parenting behaviour is backwards in the outliner 2019-09-04 21:52:47 +02:00
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Not sure how you do this, afaict, there is no CTRL+P in the outliner...

Do you have this shortcut with Factory Settings as well?
Or did you add this yourself?
Which keyconfig are you using?

Not sure how you do this, afaict, there is no CTRL+P in the outliner... Do you have this shortcut with Factory Settings as well? Or did you add this yourself? Which keyconfig are you using?
Author

You're correct, you can't do CTRL+P in the outliner. I'm using default key config.

This was my sequence of events:

Make the selections in the outliner: select the child object, followed by the parent object, while holding down SHIFT.
Move the mouse cursor back to the 3D View, and hit CTRL+P>Object(Keep Transform)
The parent relationship is created, except it's backwards. The object selected first becomes the parent, instead of the child as you would expect.

You're correct, you can't do CTRL+P in the outliner. I'm using default key config. This was my sequence of events: Make the selections in the outliner: select the child object, followed by the parent object, while holding down SHIFT. Move the mouse cursor back to the 3D View, and hit CTRL+P>Object(Keep Transform) The parent relationship is created, except it's backwards. The object selected *first* becomes the *parent*, instead of the *child* as you would expect.
Added subscribers: @WilliamReynish, @natecraddock, @JulianEisel, @mont29

@WilliamReynish @Zachman @JulianEisel Indeed in the outliner, the first selected object will be active one, while in 3DView it's always the last selected one that becomes active… Not sure whether we want to change that behavior or not?

@WilliamReynish @Zachman @JulianEisel Indeed in the outliner, the first selected object will be active one, while in 3DView it's always the last selected one that becomes active… Not sure whether we want to change that behavior or not?
Bastien Montagne changed title from Parenting behaviour is backwards in the outliner to First selected object in Outliner is active one, while it is the last selected one that becomes active in 3DView 2019-09-16 22:06:42 +02:00

@mont29 I guess we should make it consistent. It only really makes sense to parent the selected items to the active one I think.

@mont29 I guess we should make it consistent. It only really makes sense to parent the selected items to the active one I think.

@WilliamReynish parenting is totally unrelated to the issue here really… It just reveals the inconsistency in selection order (which confuses users):

  • If you select multiple objects from the Outliner, the first selected one is the active one.
  • If you select multiple objects from the 3DView, the last selected one is the active one.
@WilliamReynish parenting is totally unrelated to the issue here really… It just reveals the inconsistency in selection order (which confuses users): * If you select multiple objects from the Outliner, the **first** selected one is the active one. * If you select multiple objects from the 3DView, the **last** selected one is the active one.

@mont29 ah yes. @Zachman is working on exactly that, also so that walk selecting can change the active item. It required refactoring selecting vs activation.

@mont29 ah yes. @Zachman is working on exactly that, also so that walk selecting can change the active item. It required refactoring selecting vs activation.

I discussed this report earlier today with the author (he messaged me on Twitter). The real issue was the use of Shift+LMB for selection in the outliner. Shift is the modifier key for doing a range select. When there is an active outliner element, range select will not activate any elements. Ctrl is the modifier for extending selection + activation (equivalent to Shift click in 3D view).

So selecting in the outliner Cube.001 then Cube.002 with a Ctrl+click would indeed make the second selection (Cube.002) active.

I discussed this report earlier today with the author (he messaged me on Twitter). The real issue was the use of Shift+LMB for selection in the outliner. Shift is the modifier key for doing a range select. When there is an active outliner element, range select will not activate any elements. Ctrl is the modifier for extending selection + activation (equivalent to Shift click in 3D view). So selecting in the outliner Cube.001 then Cube.002 with a Ctrl+click would indeed make the second selection (Cube.002) active.

Added subscriber: @reed2000

Added subscriber: @reed2000
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Jeroen Bakker self-assigned this 2020-02-04 11:22:48 +01:00
Member

Seems to work as expected. There is an inconsistency between CTRL and Shift but that is done by design.

Seems to work as expected. There is an inconsistency between CTRL and Shift but that is done by design.
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
7 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#69505
No description provided.