-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AutocompleteManager + MessageKit #7
Comments
Thanks, I introduced this bug when trying to fix another. I'll push a fix soon. Sent with GitHawk |
Thanks for your patience. Still haven't fully released this yet 🙂 Sent with GitHawk |
This weekend this should be usable from |
I appreciate the help Nathan and Steven, and the update of I was able to use the I did try with the Again, the help was very much appreciated! Keep up the great work! |
How did you make to import AutocompleteManager in a MessageKit project ? When I import MessageInputBar and MessageKit, Xcode find 2 definition of multiples class because MessageKit use MessageInputBar |
@nathantannar4 Thank you |
Hey Nathan,
I've been able to get the AttachmentManager plugin working on MessageKit 1.0 from MessageInputBar 0.2 using example code written in the InputAccessoryBar 2.1, however, I am unable to successfully get AutoCompleteManager working. The problem that I find is that when I enter in the prefix, @, the table appears but is blank.
I thought this was peculiar so I then started to print out the users that were being returned in the
'
func autocompleteManager(_ manager: AutocompleteManager, autocompleteSourceFor prefix: String) -> [AutocompleteCompletion]
',and it seems to be a loop that continues to run while the prefix exists (note the scroll indicator on the right. When I started to take the screenshot, it was in the middle of scroll bar). Note, I do not find this behavior in the InputAccessoryBar project. My guess is that this would explain why the table is not being updated as the values continue to be updated too quickly for the table to register. I thought this had to do with the asynccompletions, so I removed those but to no avail.
Any help in this matter would be appreciated!
The text was updated successfully, but these errors were encountered: