Autocompletion Revamp

[andrewguilas]

The keyword “down” is used simultaneously and can be replaced with the keyword “up.”

• If the down key is pressed, the selection will go down to the field below it. If not applicable, then it would go to the next field in the next frame. If not applicable, it would restart by going in the opposite direction until not possible
• If a frame was collapsed, then the closest field of another frame would be selected. If there is no closest field, then the top closest field would take priority.
• Whenever the autocompletion fields are updated, the selection would stay the same if it is in the updated version, it not, it will restart at the top.
• If a user holds the down key, then the selection would keep on going down until the key is released. The speed of the selection changing would exponentially change.
• If the selection is out of the auto completion's context size, then the auto-completion would scroll itself

An easy approach to manage the logic would be to create a table of all the fields in the handler module every time the autocompletion was updated. If a frame was collapsed or expanded, then the proper fields would be removed or added from or to the table.

[andrewguilas]

Fix issue when collapsing a fold, it resets the selection instead of going to the closest one

Do this by getting the closest possible selection before updating the Helper.Data.Fields