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

[Code-Jack]

(Edited FR after considering discussions in other threads.)

What Do You Recommend?

For crating a new Object from a Collection, I press the “New” button in the right top.
After that appears an input field in the Grid. - Up to here it’s OK for me.

But now to the problem:
I wish that finishing the Object’s name (by pressing Enter) directly opens the new created Object for a full edit mode.
Unfortunately it isn’t so (except for Notes).

Pressing Enter finishes the input in the grid. - OK, I don’t want to complain about it. But unfortunately it doesn’t open the Object automatically.
(Maybe there’s a bug involved in my case, see Additional Context.)

Not even a second Enter opens the new Object, because it is not selected in the Grid.
So I have to use the mouse to open it. That disrupts a fluid workflow.

How Could It Be Done?

Implement a switch in the Collection’s settings:
“Directly open new created Objects for editing?”

Real World Use-Cases

I want to be able to create (and full edit) new objects quickly!
There shouldn’t be any further need for using the mouse after pressing the “New” button.

It’s an unnecessary friction in the workflow for the user that he always must switch from the keyboard to the mouse and back again.

Additional Context

Related:

Collections help

Is there a way not to open a small window when creating/renaming an object in the collections menu? When using sets that doesn’t happen, instead [image] [image] [image] [image] [image] you just give it a name and nothing pops out. It's getting quite frustating to use collections instead of sets cuz of this.

In this thread the user @SweetRoyce asks for NOT directly opening a new created Object for a full edit, but staying in the Grid instead (he speaks about Inline Sets there).

• That’s clearly the opposite of my own wish. I don’t want to stay in the Grid, instead I want directly do a full edit of the new Object.

As we see, different users prefer a different behavior in this case.
For that reason, a switch in the Collection’s and Set’s settings to choose the preferred behavior would be the best way.

Also Bugs involved?
@Filip couldn’t reproduce the behavior I described in this FR (see his post number. 11 in the linked thread above).
I experience it since some versions, actual in the v0.37.15-beta.
Maybe there’s a bug involved, so that it behaves differently for me and for other users.
But the suggested switch in the settings would also solve it nearby.

[Shampra]

Agree!
Anytype needs smoother use and less friction.

What Do You Recommend?

• Create an objet send to title editor
• In edit mode, ENTER saves the change, without losing focus
  – ENTER (again) open the (always) selected line/object
• In edit mode, TAB move to the next cell in edit mode (useful to quickly edit all relations)

Note that the behavior is different for note objects. But I understand the reasoning: it seems right to open a created note (unlike other objects, which can be defined via the title).

[Code-Jack]

@Shampra

In edit mode, TAB move to the next cell in edit mode (useful to quickly edit all relations)

Yes to all what you wrote.
But instead of Tab I would prefer to do it with Enter (for finishing the edit mode) followed by a cursor right key.

Moving through the cells in the Grid by using the four cursor keys would be intuitive for me.

But what do you thing should the Enter key do in a selected cell?
My suggestion was, to open the Object if a line is selected.
Your suggestion contains a new idea.

I think, we can even bring both ideas together:

After finishing the title in the Grid (by pressing Enter), the focus is on the whole line in the Grid.
Pressing Enter now would open the Object.
But if we not press Enter, but instead the cursor right key, the selection is no longer in the whole line, instead it jumps into the next cell right from the title.
Pressing Enter in a selected cell opens the cell edit mode.

• So we can move trough all the cells in the whole Grid by using the four cursor keys.
  Enter opens whatever is selected.
  If the whole line is selected, it opens the whole Object.
  But if only a single cell is selected, the Enter key opens the edit mode in the Grid for this particular cell.

If you ask me, that’s the way to go!
Thanks for your appreciated input, it was a missing part in my concept!

[Code-Jack]

There is a bug in v0.37.13
What I wrote in the startpost’s suggestion field is no longer the fact, it’s even worse now:
Enter doesn’t end the edit mode for the tile (Name) anymore!
But the tab key does!?!

@Razor could you please have a look?
In addition see also my last post, because of my suggestion for a general better usability.

[Razor]

I’ve already fixed it, was a mistake with Chinese input check.

[sturdily]

One thing for example, that would make it much more helpfull, would be for the “new object” in the views, to allow a similar behaviour of “right click” of the “+” button in the toolbar and show up more types.

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

[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…

[sofalakatino]

I have a similar annoyance. I create a new object, and then it’s placed somewhere within 30 other objects in the collection, and have to find it to open it and work with it. Oddly enough, there isn’t a full regularity about where in the collection it’ll be (or rather, I haven’t figured out the rules that determine that.)

[Code-Jack]

@sofalakatino

I create a new object, and then it’s placed somewhere within 30 other objects in the collection

Create a View for the Collection which is sorted for “Last modified date”.
Move this View on the first left position.
When you now create a new Object, it’s also the last modified one. So it appears on top of the View.

In the other Views it would appear on an other position, according to the sorting rules in the particular View.

[Code-Jack]

I made a strong edit of the FR after considering discussions in other threads.
The voters may have a look.