Page MenuHome
Create Task
Maniphest T87642

Needs two clicks with Ctrl or Shift key to deselect an item from a list of selected items
Needs Information from Developers, NormalPublic
Actions

Description

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

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: rB02948a2cab44

Short description of error
Needs two clicks with Ctrl or Shift key to deselect an item from a list of selected items.

Exact steps for others to reproduce the error

  • Open the project file “OutlinerSelectItemWithCtrl.blend” in attachment as a starting point.

The same problem happens in different views with different details.

Outliner:

  • Select the entire collection of objects from the collection “Item List”. You can click the “Cone” object, hold the Shift key and then click the “Torus” object to select the entire list.
  • Then hold the Ctrl key and click the Cylinder object to deselect.
  • The item’s color get a lighter color, but it is still not excluded from the whole selection.
  • Clicking a second time on the object really deselects the object.
  • If clicking the first item of the selection (which is the Cone is this example), it is deselected properly.

3D View:
The Shift key is used to select/deselect objects individually. It is pretty much the same issue. It requires two clicks on the same object to really deselect the object, whatever the order of the object in the selection. However, if one object has already been selected before deselecting everything, then the same object gets selected with an additional highlight from the new selection (dragging the mouse cursor in the viewport).

Shading view:
Pretty similar to the 3D view.
If I deselect all the nodes (Alt + A for example) and I drag the mouse cursor to select all nodes, the last selected node is highlighted in white. If I click the node highlighted in white while holding the Shift key, the node is deselected. However, if I do the same thing for the other nodes, it selects the node with a white highlight and I have to click a second time on the same node to really deselect it. The behavior of the last selected item is also present in the 3D View, but not for the Outliner.

The Compositing view has the same problem and I suspect that the Geometry Node view has the same too (I haven’t tested the last one).

In general, it requires two clicks to deselect an object with the normal behavior.

The first click behaves as an “add to selection” click unless the object already had a selection before completely creating a new selection.

In all cases, there is an issue with deselecting (or excluding) and single object from a selection of objects in different views. As a reference how it should behave correctly, the Windows Explorer in Windows is able to deselect a single item on the first time it is clicked.

OutlinerSelectItemWithCtrl.blend1 MBDownload

Event Timeline

Sebastien Larocque (SebBlender) created this task.Apr 19 2021, 9:09 PM
Dan Pool (dpdp) added a subscriber: Dan Pool (dpdp).Apr 19 2021, 10:43 PM

Not really a bug. The first click makes the clicked object the active object. The second click deselects it. I feel this is not great behavior and the first click on a shift-click should deselect the object. However, we still need a way to change which object is the active object.

Sebastien Larocque (SebBlender) updated the task description. (Show Details)Apr 20 2021, 12:49 AM
Sebastien Larocque (SebBlender) added a comment.Apr 20 2021, 1:16 AM

It might not be a bug, but certainly it is an issue. There are two things important to highlight.

  1. When looking at other applications on Windows, and probably other operating systems, it works in a more direct way. Holding the Ctrl key when clicking any item deselects the item without this notion of an already selected item from a previous selection.
  1. Yes, it seems to have an active object being taken into account. However, it is cumbersome to have to check if the object is already selected. If I don’t check that, I still have to check if I need to click a second time on the object. It is certainly not productive.

After making many tests, there seems to have this notion of an active object already selected before influencing the new selection. If someone doesn’t know that, they will try to manage the selection with what is already known with 99% and + of other programs.

I’m aware that Blender has a more special interface design. However, I reported it because it did not work as I expected. The list selection management is something that I consider standard in terms of UI design.

Pratik Borhade (PratikPB2123) added a project: User Interface.Apr 22 2021, 12:12 PM
Pratik Borhade (PratikPB2123) added a subscriber: Pratik Borhade (PratikPB2123).

Thanks for the report. Not sure if this is intended behavior or not, so adding module tag.

Pratik Borhade (PratikPB2123) changed the task status from Needs Triage to Needs Information from Developers.Apr 22 2021, 12:12 PM