IC Keymap: Delete Objects from Outliner Shortcut broken #74422

Closed
opened 2020-03-04 09:40:55 +01:00 by Debuk · 14 comments

System Information
Operating system: Windows-10 - 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007

Blender Version
Broken: version: 2.83 (sub 5), branch: master, commit date: 2020-03-01 21:35, hash: eaf0528749
Worked: perhaps long time ago.

Short description of error
Having chosen the IC Keymap there are shortcuts mapped to
outliner.object_operation - Delete to backspace and delete with press. These can't be triggered.

So deleting collections work but deleting objects isn't reachable

Possible Solution:

Changing their triggering method to "Release" works

**System Information** Operating system: Windows-10 - 64 Bits Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007 **Blender Version** Broken: version: 2.83 (sub 5), branch: master, commit date: 2020-03-01 21:35, hash: `eaf0528749` Worked: perhaps long time ago. **Short description of error** Having chosen the IC Keymap there are shortcuts mapped to *outliner.object_operation* - *Delete* to backspace and delete with press. These can't be triggered. So deleting collections work but deleting objects isn't reachable **Possible Solution:** Changing their triggering method to "Release" works
Author

Added subscriber: @Debuk

Added subscriber: @Debuk
Author

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish
Author

@WilliamReynish Could you please have a look.

@WilliamReynish Could you please have a look.

Closed as duplicate of #67462

Closed as duplicate of #67462

Added subscriber: @natecraddock

Added subscriber: @natecraddock

This is due to the fact that deleting collections and objects are two different operators, and Blender doesn't know which one to use automatically. It's a todo:

https://developer.blender.org/T67462

I believe @Zachman is working on a fix for this issue.

This is due to the fact that deleting collections and objects are two different operators, and Blender doesn't know which one to use automatically. It's a todo: https://developer.blender.org/T67462 I believe @Zachman is working on a fix for this issue.
Author

Yes obviously it's a duplicate, sorry for that. But that's from July 2019

Why don't you implement that two clicks to fix it in the meantime with the workaround solution. That's broken since month and needs seconds to fix. Maybe a more elegant solution is somewhere around the corner.

But I don't get why so simple fixes get suspended.

Yes obviously it's a duplicate, sorry for that. But that's from July 2019 Why don't you implement that two clicks to fix it in the meantime with the workaround solution. That's broken since month and needs seconds to fix. Maybe a more elegant solution is somewhere around the corner. But I don't get why so simple fixes get suspended.

@Debuk perhaps @Zachman could chime in to clarify how hard (or not) this would be to fix in the Outliner. It's certainly super annoying, and an issue lots of users face.

@Debuk perhaps @Zachman could chime in to clarify how hard (or not) this would be to fix in the Outliner. It's certainly super annoying, and an issue lots of users face.
Author

@WilliamReynish: Hi William, yes it's certainly annoying. And it's like that for no reason.

Sure would it be somehow interesting to know when this topic is treated by him.

But to me that's not the point. This is lying around since last July, it's wrong to assume that it will be solved very soon.

What I tried to say is, it's in your hands to change these two shortcuts to "release" as proposed and solve this meanwhile until whatever change is done inside the outliner. This change is so minimal that it doesn't conflict with his development.

Couldn't you write him a note into his todo task that you changed them to release and that he should switch it back while he's coding it?

@WilliamReynish: Hi William, yes it's certainly annoying. And it's like that for no reason. Sure would it be somehow interesting to know when this topic is treated by him. But to me that's not the point. This is lying around since last July, it's wrong to assume that it will be solved very soon. What I tried to say is, it's in your hands to change these two shortcuts to "release" as proposed and solve this meanwhile until whatever change is done inside the outliner. This change is so minimal that it doesn't conflict with his development. Couldn't you write him a note into his todo task that you changed them to release and that he should switch it back while he's coding it?

Hi @Debuk, I definitely had hoped to work on this sooner, but as a university student life got in the way :(

I agree that this issue is very frustrating. A quick solution like you said is to add outliner_object_operation to all the keymaps under release for both X and Delete keys. That is fine to me (wonders what @WilliamReynish thinks) because I think a proper solution would take time.

Hi @Debuk, I definitely had hoped to work on this sooner, but as a university student life got in the way :( I agree that this issue is very frustrating. A quick solution like you said is to add `outliner_object_operation` to all the keymaps under `release` for both X and Delete keys. That is fine to me (wonders what @WilliamReynish thinks) because I think a proper solution would take time.
Author

Added subscriber: @billrey

Added subscriber: @billrey
Author

Hi @Zachman, no worries. I know pretty well how it was during that time. Thanks for your valuation.

@billrey What do you think of this workaround solution?

Hi @Zachman, no worries. I know pretty well how it was during that time. Thanks for your valuation. @billrey What do you think of this workaround solution?

In my opinion assigning one for press and one to release sounds like a bad hack, which can cause other issues and conflicts. There's also a danger that the issue is then never properly addressed. I would rather see this done right, so that there is just a single delete operator in the Outliner which is context sensitive. Hopefully it's not a massive project to do this, once a developer is working on it.

In my opinion assigning one for **press** and one to **release** sounds like a bad hack, which can cause other issues and conflicts. There's also a danger that the issue is then never properly addressed. I would rather see this done right, so that there is just a single delete operator in the Outliner which is context sensitive. Hopefully it's not a massive project to do this, once a developer is working on it.
Author

@billrey I can see the reasoning, but as @Zachman is also engaged to get this done, I'd wish blenders policy to treat things like this would rather consider that there are people out there using blender as part of their productive environment, than judging on if something feels like a hack.

@billrey I can see the reasoning, but as @Zachman is also engaged to get this done, I'd wish blenders policy to treat things like this would rather consider that there are people out there using blender as part of their productive environment, than judging on if something feels like a hack.
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
3 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#74422
No description provided.