Skip to content

Conversation

ArshAulakh59
Copy link

Note:
These changes were made to better use awesome library in one of my projects. Change log is as follows:

  1. Added presenterView property to manually pass in a view onto which you would want to add the completion table. This fixes the issues regarding table scrolling and table cell selections.
  2. Changed variables to IBInspectables so its much easier now to use the library in IB.
  3. Updated codebase
  4. Cleaned up codebase
  5. Removed custom font option for autocomplete text (as it was not required in my project)

Thanks.

@wvdk
Copy link

wvdk commented Jul 1, 2016

I just ran a quick test of this fork on device. The autocomplete isn't showing up. Are you sure it's working for you? If so, I can look into it further on my end.

@ArshAulakh59
Copy link
Author

@wvdk Yes I'm using it in one of my projects and its working pretty well.
I'll add a gif to support my statement.
autocompletioninaction

@ArshAulakh59
Copy link
Author

@wvdk I think I know where the problem lies with it not working for you.
I've added a presenterView property to the textfield which needs to be hooked up in IB as that view is then used to house the autocomplete table.
I did this because of the various touch detection problems that people complained of and also in my case my textfield was inside a cell (hence causing the touch to not get detected on the cells outside the container view). So I took this approach and made the table show up on my main view and now it all works like a charm.
Also this approach is more robust as it can easily handle cases such as mine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants