Multiple objects selection problem #76762

New Issue

Sergey · 2020-05-14T19:56:08+02:00

Sergey commented

2020-05-14 19:56:08 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92

Blender Version
Broken: version: 2.90 (sub 1), branch: master, commit date: 2020-05-11 21:02, hash: 542ff416e2
Worked: (newest version of Blender that worked as expected)

Short description of error
When selecting several objects, the last active object is selected implicitly (and it is not shown as active).

I believe that a more predictable behavior would be to make the active object one (random) object from the set of selected.

Exact steps for others to reproduce the error
1 - create 3 cubes
2 - select first cube
3 - deselect all object
4 - select second and third cubes by dragging (box selection or lasso selection)
Result: we have 2 cubes selected in the viewport. Not one of these cubes is active. But implicitly the first cube still selected (
if we look at the properties of the object, these will be the properties of the first cube)

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 **Blender Version** Broken: version: 2.90 (sub 1), branch: master, commit date: 2020-05-11 21:02, hash: `542ff416e2` Worked: (newest version of Blender that worked as expected) **Short description of error** When selecting several objects, the last active object is selected implicitly (and it is not shown as active).![selection.PNG](https://archive.blender.org/developer/F8535779/selection.PNG) I believe that a more predictable behavior would be to make the active object one (random) object from the set of selected. **Exact steps for others to reproduce the error** 1 - create 3 cubes 2 - select first cube 3 - deselect all object 4 - select second and third cubes by dragging (box selection or lasso selection) Result: we have 2 cubes selected in the viewport. Not one of these cubes is active. But implicitly the first cube still selected ( if we look at the properties of the object, these will be the properties of the first cube)

Sergey commented

2020-05-14 19:56:08 +02:00

Added subscriber: @borschberry

Sergey changed title from ~~Multiple objects secetion problem~~ to Multiple objects selection problem

2020-05-14 19:58:41 +02:00

Ankit Meel commented

2020-05-14 21:07:58 +02:00

Added subscribers: @natecraddock, @ankitm

Ankit Meel commented

2020-05-14 21:07:58 +02:00

@Zachman I remember asking you this some weeks ago in chat. Is this already planned in some task?
As of now, it is a request for modified behaviour

@Zachman I remember asking you this some weeks ago in chat. Is this already planned in some task? As of now, it is a request for modified behaviour

Sergey commented

2020-05-14 21:24:26 +02:00

@ankitm It seems to me that the active object should be at least highlighted. And despite the fact that it is active, operations like transform rotate, etc. are not applied to it.

Nathan Craddock commented

2020-05-15 00:21:06 +02:00

@ankitm maybe I was talking about the Outliner selection in the chat? This is how Blender is expected to behave with selection, and it has behaved this way for as long as I can remember. I checked 2.79, but I don't believe this behavior has been any different going back to 2.5x. There is a distinction between the active object and selection, or put another way, not all selection operators do activation.

I believe that a more predictable behavior would be to make the active object one (random) object from the set of selected.

I don't think predictability and randomness go together very well, which may be one reason why Blender does not arbitrarily set active objects. I also don't get how this is "bad" behavior.

@ankitm maybe I was talking about the Outliner selection in the chat? This is how Blender is expected to behave with selection, and it has behaved this way for as long as I can remember. I checked 2.79, but I don't believe this behavior has been any different going back to 2.5x. There is a distinction between the active object and selection, or put another way, not all selection operators do activation. >I believe that a more predictable behavior would be to make the active object one (random) object from the set of selected. I don't think predictability and randomness go together very well, which may be one reason why Blender does not arbitrarily set active objects. I also don't get how this is "bad" behavior.

Brecht Van Lommel commented

2020-05-15 00:32:29 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2020-05-15 00:32:30 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Brecht Van Lommel closed this issue

2020-05-15 00:32:30 +02:00

Brecht Van Lommel self-assigned this 2020-05-15 00:32:30 +02:00

Brecht Van Lommel commented

2020-05-15 00:32:30 +02:00

This is indeed how Blender works by design, and has worked for a long time. Any proposed changes here are outside the scope of the bug tracker.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Multiple objects selection problem #76762