The JADE 2022 release meets tomorrow’s business demands.
This idea has been merged into another idea. To comment or vote on this idea, please visit JAD-I-468 Auto-complete, pressing dot not to automatically select.
When autocomplete is set to match on history first, it is possible to have typed in the exact name of an item, and not have this item selected.
e.g.
Two local variables, object and objectCopy
If I had just done something with objectCopy, this is the last thing in my history list.
If I then type in object, autocomplete will highlight objectCopy, even though there is an item that matches what I have typed in exactly
Blake De'Ath
Hi Blake,
FYI: Once you're on Jade 2018, if you unset the Use History for Selection option in the Auto Complete group of the Editor Options tab in your preferences, then it would 'correctly' select object not objectCopy in your example work-flow.
Cheers,
BeeJay.
If I have a local variable say 'l', it will never show up in autocomplete the local variable. Same goes for a recently added property. It exists in the super class with the prefix all. I start typing all and it suggests call but the newly created reference is no where to be seen. For determining the list (but keeping the same order) should it start with local variables, and move up the chain of inheritance?