Blender 2.8. Turn off 4,5,6,... collections visability hotkeys when you inside edit mode. Often press wrong [nearby] key ["4"] #62841

Closed
opened 2019-03-22 13:09:29 +01:00 by Ruslan · 12 comments

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35

Blender Version
Broken: version: 2.80 (sub 51), branch: blender2.7, commit date: 2019-03-21 23:13, hash: 1ae6aaad43

Short description of error
Turn off 4,5,6,... collections visibility hotkeys when you in edit mode. I found myself always frustrate when I want to turn on edit mode[face], but suddenly press key 4 and after that I need to restore[revert] visability of all layers back. It happens quite often and very annoying.
At first I post in on RightClick but there Pablo says "Pablo Vazquez: That's more of an oversight from the implementation than a feature proposal. Please report it!"1111111111111.jpg

Exact steps for others to reproduce the error
Open default. Create 4-5 different standart objects and put each of them in to separete collection. Then choose one of first 3 object [in outliner list] and press edit mode. Then press button 4, and you will se that current object with edit mode dissapeared and from collection 4 will arise in usual mode.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35 **Blender Version** Broken: version: 2.80 (sub 51), branch: blender2.7, commit date: 2019-03-21 23:13, hash: `1ae6aaad43` **Short description of error** Turn off 4,5,6,... collections visibility hotkeys when you in edit mode. I found myself always frustrate when I want to turn on edit mode[face], but suddenly press key 4 and after that I need to restore[revert] visability of all layers back. It happens quite often and very annoying. At first I post in on RightClick but there Pablo says "Pablo Vazquez: That's more of an oversight from the implementation than a feature proposal. Please report it!"![1111111111111.jpg](https://archive.blender.org/developer/F6865087/1111111111111.jpg) **Exact steps for others to reproduce the error** Open default. Create 4-5 different standart objects and put each of them in to separete collection. Then choose one of first 3 object [in outliner list] and press edit mode. Then press button 4, and you will se that current object with edit mode dissapeared and from collection 4 will arise in usual mode.
Author

Added subscriber: @rs2128

Added subscriber: @rs2128
Ruslan changed title from Turn off 4,5,6,... collections visability hotkeys when you inside edit mode. Often press wrong [nearby] key ["4"] to Blender 2.8. Turn off 4,5,6,... collections visability hotkeys when you inside edit mode. Often press wrong [nearby] key ["4"] 2019-03-22 13:10:15 +01:00
Added subscribers: @ideasman42, @pablovazquez, @WilliamReynish

@pablovazquez @ideasman42

This behavior definitely seems wrong. If we are using the 1-3 number keys for the selection modes, it makes no sense to keep 4-9 for Collection visibility.

I think we should just not use 4-9 in Edit mode - this frees up keys for users to add hotkeys to tools as they wish instead.

I still think switching collections with 1-9 in object mode is also weak, simply because it's not predictable and screws up your scene visibility too easily, but that's another issue.

@pablovazquez @ideasman42 This behavior definitely seems wrong. If we are using the 1-3 number keys for the selection modes, it makes no sense to keep 4-9 for Collection visibility. I think we should just not use 4-9 in Edit mode - this frees up keys for users to add hotkeys to tools as they wish instead. I still think switching collections with 1-9 in object mode is also weak, simply because it's not predictable and screws up your scene visibility too easily, but that's another issue.

Disabling these keys in edit-mode seems reasonable (all edit modes, then the keys can be free in other edit-modes too).

Disabling these keys in edit-mode seems reasonable (all edit modes, then the keys can be free in other edit-modes too).

@ideasman42 Yes, agreed. Then it's nicely consistent, and users can use those keys in all the edit modes.

@ideasman42 Yes, agreed. Then it's nicely consistent, and users can use those keys in all the edit modes.

Added subscriber: @brecht

Added subscriber: @brecht
Dalai Felinto was assigned by Brecht Van Lommel 2019-03-22 15:21:41 +01:00

This was changed for studio/blender-studio#55921 (Toggling visibility for collections doesn't work in Pose mode), but should only apply to object and pose mode and I think.

This was changed for studio/blender-studio#55921 (Toggling visibility for collections doesn't work in Pose mode), but should only apply to object and pose mode and I think.
Member

In #62841#646255, @WilliamReynish wrote:
I still think switching collections with 1-9 in object mode is also weak, simply because it's not predictable and screws up your scene visibility too easily, but that's another issue.

Agreed. Collections in reality are more complicated than just 1-9. Not a topic for this bug though, let's talk about it during the homestretch.

> In #62841#646255, @WilliamReynish wrote: > I still think switching collections with 1-9 in object mode is also weak, simply because it's not predictable and screws up your scene visibility too easily, but that's another issue. Agreed. Collections in reality are more complicated than just 1-9. Not a topic for this bug though, let's talk about it during the homestretch.

This issue was referenced by a17df6d91e

This issue was referenced by a17df6d91e6806186c7416669c61950b763fe665

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Added subscriber: @DavidKozma

Added subscriber: @DavidKozma

In #62841#646314, @pablovazquez wrote:
Agreed. Collections in reality are more complicated than just 1-9. Not a topic for this bug though, let's talk about it during the homestretch.

Hey Pablo, have you ever ended up discussing this?
This is pretty bad UX, I'm constantly hitting them accidentally either by misclicking Q and W or just because I think I'm in edit mode.
I just figured I can undo this with Ctrl+Z but before that I was trying all modifier key combinations if I can maybe reverse what I just did. There was no way.
Also I'm working with tons of nested collections now. This high level hide doesn't help me much. I rather "exclude them from view layer" if anything.

I know, I can turn them off in the keymap (and I just did) but I still think this should be up for debate as a default behavior.

Cheers

> In #62841#646314, @pablovazquez wrote: > Agreed. Collections in reality are more complicated than just 1-9. Not a topic for this bug though, let's talk about it during the homestretch. Hey Pablo, have you ever ended up discussing this? This is pretty bad UX, I'm constantly hitting them accidentally either by misclicking Q and W or just because I think I'm in edit mode. I just figured I can undo this with Ctrl+Z but before that I was trying all modifier key combinations if I can maybe reverse what I just did. There was no way. Also I'm working with tons of nested collections now. This high level hide doesn't help me much. I rather "exclude them from view layer" if anything. I know, I can turn them off in the keymap (and I just did) but I still think this should be up for debate as a default behavior. Cheers
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
8 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#62841
No description provided.