[Feature Request] Adding enum values to a Tmap in editor automatically defaults to the next unused enum value, not the first one

When editing a TMap in the blueprints, when you add a second element, it defaults to adding the first value in the enum class, in my case, the color red.

Because you can’t have two of the same key values, I have to be constantly changing each item from red to a different color, which, not only is a big pain, especially if one’s enum list is very long, it makes it impossible to have the values in the order that you want them to be in, ie, the order you have them in the enum list.

How this should work instead, is that, when you hit “add,” the value that comes out is the next unused value.

So for me, that would mean first time I hit it, red comes out, then blue, then green, and this would happen automatically, instead of me having to change it everytime and it will be in the order I want them in.

And it will add in the next available value, as in the lowest, not already used value, not the next value coming after the one before it. So if I added red, then added the next one, which would be blue, but I change that to green. When I add the third element, it will be blue again as that is the lowest value not used.