[kovarex] [2.0.21] Confirmation shortcut ('E') on icon select for save name confirms the save dialog

[dandi345]

Hello,

I hope this qualifies as a Bug, at least it is unexpected behavior for me.

• What did you do?

I wanted to create a save with an icon in the save name.
Since I have quality enabled the selection doesn't auto confirm when clicking.
I tried to confirm the icon selection with the shortcut 'E' directly after clicking.

• What happened?

Instead of adding the icon to the save name the save was created without the icon in the name.
It looks like the shortcut confirmed the save dialog in the background instead of the icon selection.

• What did you expect to happen instead? It might be obvious to you, but do it anyway!

I expected the icon to appear in the save name and the name to be further editable afterwards.
For other similar cases this is what happens (train stop and blueprint dialogs stay open and insert the correct icon into the name when pressing 'E')

• Does it happen always, once, or sometimes?

It happens every time.
It is just a minor inconvenience, just breaks my muscle memory for these dialogs.

Best regards

[Game_Ender]

I am plagued by this issue as well. It hits me harder because I like checkpoint saves along the way vs. a single save that I constantly overwrite. I also use Icons frequently in many other dialogs so muscle memory is strong.

The result is I have to save about 1/3 of my games my games twice . Once with a name like "SPACE -" then once with a name like "SPACE - Finally have quality working".

[zin]

I am plagued by this issue as well. It hits me harder because I like checkpoint saves along the way vs. a single save that I constantly overwrite. I also use Icons frequently in many other dialogs so muscle memory is strong.

The result is I have to save about 1/3 of my games my games twice . Once with a name like "SPACE -" then once with a name like "SPACE - Finally have quality working".

I do exactly the same thing as you. It’s eerie how similar we are.

Anyway, this issue is frustrating, and I hope that it is fixed! (The bug still occurs in 2.0.23.)