https://projects.qnetp.net/2013-04-11T18:55:46+02:00Projects hosted by qNETpSmuxi - Task #829: let the engine handle autocompletehttps://projects.qnetp.net/issues/show/829?journal_id=18972013-04-11T18:55:46+02:00Mirco Bauer
<ul></ul><p>This is a bad idea as it would need a round-trip to the engine. Or do you suggest to make them happen in the background and only update when the result was received?</p> Smuxi - Task #829: let the engine handle autocompletehttps://projects.qnetp.net/issues/show/829?journal_id=19012013-04-11T19:04:47+02:00Oliver Schneider
<ul></ul><p>no that'll be very odd, you're right, roundtrip sucks.</p>
<p>how about giving each chat model a list of autocomplete strings then?</p>
even better: removing this from entry:<br />
<pre>
// return if we don't support the current ChatView
if (!(ChatViewManager.CurrentChatView is GroupChatView) &&
!(ChatViewManager.CurrentChatView is PersonChatView)) {
return;
}
</pre>
<p>and making it ask the current view (by a virtual function in chatview) for an autocompletion</p> Smuxi - Task #829: let the engine handle autocompletehttps://projects.qnetp.net/issues/show/829?journal_id=19712013-05-31T16:30:12+02:00Ondrej Hošek
<ul></ul><p>Can we consider this solved after my rewrite of the completion infrastructure?</p>