On 04/24/2017 05:35 PM, Dr. Marcel
That's indeed a limitation/blurry area of async content assist
implementation so far. Assistance on this topic would be welcome ;)
the problem that remains (or I don’t see a solution
for yet) is the proposal ordering. How do you order proposals
from engines that may take longer? Is this deterministic (i.e.,
is the proposal order understandable for the end user)? Or do
you just by put new proposals at the bottom as soon they arrive?
I guess putting them "in between” given some priority value is
not what you do?