Currently using setItems will not result in an update of the potential matches, because filtering will be done using the - by then - old items contained in the current model.
I ran into that, while continually updating the items on user input with completions returned by a remote server. The completions were always 'one char behind'. :D
To make sure, this actually solves the problem, I went ahead and copied the updated code into my project and tried it - with success.
If you need anything else, or this was in fact intended, let me know. :)
Currently using
setItems
will not result in an update of the potential matches, because filtering will be done using the - by then - old items contained in the currentmodel
.I ran into that, while continually updating the items on user input with completions returned by a remote server. The completions were always 'one char behind'. :D
To make sure, this actually solves the problem, I went ahead and copied the updated code into my project and tried it - with success.
If you need anything else, or this was in fact intended, let me know. :)
Besides that, nice API changes in 3.0!