SelectOrDeselectAll (on LMB) Breaks LMB Selections (2.80) #57131

Closed
opened 2018-10-10 07:50:34 +02:00 by 0rAngE · 6 comments

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:
http://edge-loop.com/images/blender/support/SelectOrDeselectAll_x246.avi

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:
    http://edge-loop.com/images/blender/support/2.80_SelectOrDeselectAll_BUG.zip
**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: http://edge-loop.com/images/blender/support/SelectOrDeselectAll_x246.avi **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: http://edge-loop.com/images/blender/support/2.80_SelectOrDeselectAll_BUG.zip
Author

Added subscriber: @0rAngE

Added subscriber: @0rAngE
0rAngE changed title from SelectOrDeselectAll (on LMB) Breaks LMB Selections to SelectOrDeselectAll (on LMB) Breaks LMB Selections (2.80) 2018-10-10 15:14:16 +02:00
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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) view3d.select [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 view3d.select 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...)

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) view3d.select [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 view3d.select 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...)
Author

Just wanted to confirm, that you are correct.
When I unmap view3d.select [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!

Just wanted to confirm, that you are correct. When I unmap *view3d.select [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!
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Philipp Oeser self-assigned this 2018-10-15 09:10:36 +02:00
Member

Glad to hear, closing then...

Glad to hear, closing then...
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
2 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#57131
No description provided.