Maps are sorted containers. This mean that map is kept sorted by the “key” value all the time. There is never a guarantee that he last element will be the last element you’ve inserted. In fact it is guaranteed that the last element will be the one with the highest “key” value. Have you noticed that the words “one”, “four”, “three” and “two” are in alphabetical order? This increases the search speed tremendously when you are working with large maps. (although it decreases the insertion speed)
You’ve totally missed the point. The blueprint editor does not show all the values in the map and deleting values from the map does not truly remove them, although they disappear from the editor display. Renaming the key in the editor creates a whole new node instead of replacing the existing key/value pair.
No problem. An interesting extra tidbit is that the blueprint editor works properly for a map if it’s a variable within the test blueprint in regards to adding, deleting, and changing key values. It’s only when it’s in a blueprint structure component that it exhibits these problems.
