Implement a swich: "should this Collection directly open new created Objects for editing?" (edited FR)

[Shampra]

@sturdily

Creating a new object and then switching the type (and template) isn’t great

Agree I talked about it here but didn’t take the time to open a ticket.

Feedback : transpose a whisky base

Usercase : trying to port a whisky base (from MySQL/web) [image] Feeling weary of maintaining a personal website for managing tasting notes, I decided to make the switch to Anytype, harboring high hopes. I think, I hope, that detailing the experience helps put Anytype’s little (or big) annoyances into perspective? I add open topics when there are any. Here’s my feedback! Creating the database Full of hope, I export my database in CSV format, import… But I can’t change the relations, it’s al…

For my initial view, I opt for the Gallery. I add a grid view to quickly add/edit relations. I create a few more bottles, open one, and , it’s not the default template! I just realized that you can choose a default template for each view, BUT if you create an object with another template, it becomes the new default template! Why? Perhaps there’s room for improvement here (click on a template to create an object with that template; use the “define by default” option to set it as default; don’t mix expected actions).

Edit : done!

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 “Ch…