Page MenuHome

[Collections] ~ "+ New Collection" option only available for collections already containing sub-collections
Closed, InvalidPublicDESIGN


System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: rB77d23b0bd76f

Short description of error
When I hit "M" to move an object into a collection, the option to create a new collection under an existing one only appears if there already is at least one sub-collection present.
Please refer to the attached screenshots for a visual reference to what I'm talking about. ^^'

Exact steps for others to reproduce the error

  • Create a new Collection in the Scene Collection (Collection 2)
  • Create a new Collection within Collection 2
  • Select any object, press "M" and you'll see there is no "+ New Collection" entry for empty collections.

Event Timeline

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.Mon, Feb 17, 1:05 PM
Germano Cavalcante (mano-wii) updated the task description. (Show Details)
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Design".Mon, Feb 17, 1:34 PM

This is more of a feature request than a bug, setting as a design task since it is something that can be implemented.

On second thought, this is something that needs to be discussed.
Having to choose the option in the submenu can be more of a hindrance than a help.

For suggestions on how to improve the UI, please use other channels:

I can see this being a very low priority task, but why a "hindrance"?! =O

I can see this being a very low priority task, but why a "hindrance"?! =O

It gets in the way because you need to wait or click to enter the submenu and thus choose the same collection pointed in the previous menu to move the object to this collection.

Going through the outliner just to add a sub-collection is 10x worse, to me, especially when it starts getting crowded.
That extra second to wait for the sub-menu to open is nothing, in comparison.
Furthermore, if there's at least one sub-collection present we already have to wait for the sub-menu to open, thus this particular design choice is a (disputable) improvement only in a very limited range of cases.
Statistically speaking, it's actually an "anti-improvement".

This is the just the practical point of view of a user, of course.

I understand your concern, but I cannot confirm this type of design without having it discussed.
Please use the other channels provided.
Or contact @William Reynish (billreynish)

Sorry, when you said it needed to be discussed I thought I was going to be a participant in the discussion.
I have already posted the issue on one of the "provided channels".
Thank you.

PS: how do I contact the person you mentioned?