In typing name of new node show possible matches which can be selected for the node

[peterprib]

In adding a new node the node may already exists. Thus this feature shows the possible match. Saves having to do a search and helps minimize duplication of nodes.

[Phillipus]

With a very large model there will be a bad performance hit as the model is searched for matching names as each letter of the name is typed.

[Phillipus]

Just did a POC test. It could be done but all concept names would need to be cached. Also, this comes under the general heading of "warn users if they type a duplicate name" which could apply also to the models tree, the property view, rename actions, undo/redo actions and possibly other places.

[Phillipus]

Closing this one as we already have #377

[peterprib]

Different from duplicate name as suggesting it can then select one of the list plus match should not be word order dependent which could be done by hash maps which should overcome performance problems mentioned

[Phillipus]

OK, I'll re-open it but they are connected issues.

Note, keeping lookup tables in sync with a changing model is not easy.

[peterprib]

Didn't mean to imply not connected just the other is a small subset. Suggest its a case of "close enough is good enough", that is, if there are a few exceptions does it matter more so if phonetics and synonyms recognition added along with removal of noise words such as "a", "the", "to"..... Its use is just an aid so accuracy doesn't have to be perfect.