Page MenuHome

SelectOrDeselectAll (on LMB) Breaks LMB Selections (2.80)
Closed, ResolvedPublic


System Information
Operating system and graphics card
Win7 64 Ult, GeForce GTX 1060 6GB

Blender Version
Broken: blender-2.80.0-git.e1293da0140-windows64
Worked: (optional)

Short description of error
view3d.select_or_deselect_all is breaking the selection of occluded objects when bound on LMB, and using LMB as Select. This was not the case with the 2.7x series
Video showing the bug:

Exact steps for others to reproduce the error

  • Run Blender 2.8 with Default Settings.
  • Blender User Preferences > Input TAB > 3D View > 3D View(Global), Scroll to bottom, > Add New > view3d.select_or_deselect_all, bind to LMB
  • (EDIT: forgot to mention this) Blender User Preferences > Input TAB > SelectWith: Left
  • Shift + A > Add Mesh > Plane; Scale it; G Z -1 (to move to the bottom of the default cube)
  • Try selecting the Cube

Or use this 2.8 Config Setup that has all that already made:

Event Timeline

0rAngE (undo) renamed this task from SelectOrDeselectAll (on LMB) Breaks LMB Selections to SelectOrDeselectAll (on LMB) Breaks LMB Selections (2.80).Oct 10 2018, 3:14 PM
0rAngE (undo) updated the task description. (Show Details)
0rAngE (undo) updated the task description. (Show Details)
Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to 30.Oct 12 2018, 9:47 AM

Unless I am misunderstanding something here, I am seeing the exact same behaviour in 2.79b / 2.78c as well.
Could you show us this is working in 2.7x?

This also seems like expected behaviour: If you set this up like you do, you are effectively selecting twice:

  • (1) [mapped to Mouse > Selection Mouse]
  • (2) view3d.select_or_deselect_all [mapped to Mouse > Left]

select_or_deselect_all is just a python wrapper and will [next to some other stuff] eventually call as well...

And if you select twice in the same location [without you setup, just in default blender], blender will first select the closest object, for the second click: select the next-closest object.
So if you have two objects this might look like selection isnt working but if you put 3 or more objects in depth you will see blender is still cycling through the different objects.

That being said (and without knowing what you actually want to achieve here), your setup will work as far as I can see if you disable the 'regular' selection keymap item mentioned in (1)

Marking as incomplete until we know if this is solved (or if there is something else going on...)

Just wanted to confirm, that you are correct.
When I unmap [mapped to Mouse > Selection Mouse] it works.
I used to need that in the 2.6-2.7x series, that's why I left it on when I started recreating my setup on 2.80

Thanks for looking into this!
Appreciate all the hard work you guys are doing!

Philipp Oeser (lichtwerk) changed the task status from Unknown Status to Resolved.Oct 15 2018, 9:10 AM
Philipp Oeser (lichtwerk) claimed this task.

Glad to hear, closing then...