Clearly separate the creation choice and the default choice for object creation from set/collection

What Do You Recommend?

On set/collection, we have :

  • definition of a default object
  • the choice of creating an object other than the default one
    But if you create an object other than the default, it becomes the default object, so it shouldn’t!

Worse for templates: a menu clearly proposes to define a default one, which is good. But even if you just click on a template to use it just once, it becomes the default.

How Could It Be Done?

  • If a user wants to choose default, he must use a clear “Choose as Default” option
    This option already exists for template.
  • create create a non-default object/template must not set it as the default object/template

Real World Use-Cases

I have a collection of stuff, so “stuff” is define as default object with the most used template as default too.
But sometimes, I need to ad a “thing” object; or a stuff object with another template : but I don’t want to loose the default configuration!

Additional Context

It’s not too serious, but it’s bound to cause problems from time to time. As others have mentioned, we might as well open a ticket to see if the UX can’t be improved.

Only disagree with this part! Collections are awesome, as long as they are easy/practical to use!
It must be as easy to create an object on a collection as it is to create an object outside of it.

It is like in windows or linux, you are inside a folder, and every time you create a new folder or file inside of it, you have to move it there!

Another option is to have a Set which enabled the “linked to” by default. (this would even enable automaticly linking an object to multiple collections)

EDIT: also don’t forget to self vote on your FR

it’s not too serious… for me. :sweat_smile:
There are other problems or elements to review that impact me much more (and mean that I can’t really use Anytpe at the moment).
Which also explains why I don’t have a vote for this request, I posted it simply because it would improve the consistency and usability of the interface.
Any change for the better is welcome (and therefore worth sharing :)).

Ohh ok, its fair :slight_smile: