-
Notifications
You must be signed in to change notification settings - Fork 222
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
AutoCompleteTableView loses user interaction when displayed over a sibling table cell #82
Comments
To work around this, you can assign the For example:
|
I'm having the same issue - however I can't find the autoCompleteParentView field. Are you sure thats the correct name? |
OH! I am sorry! One of our developers added this property and I did not check for that. It might be good to prepare a pull request for that 😯 |
Hi,
|
@theoriginalgri |
+1 |
@theoriginalgri could you please merge the changes you mentioned regarding parentView? It would be great to have it by default in pod. Thank you beforehand. |
@theoriginalgri @EddyBorja This still doesn't work for me... when I set the parent view to |
I have tried to solve a more general problem:
I have tested this approach when the MLPAutoCompleteTextField is inside a tableView. |
I'm using MLPAutoComplete TextFields in my project, in several textfields in dynamic table cells. It works perfectly when the cell's row is large enough to fit the entire AutoCompleteTableView (scrollable list of suggestions). However, if the row height is smaller than the auto suggestion window, the user interaction is not being picked up by the 'scrollable auto suggstion window' and instead of scrolling through the suggestions, it is making my tableview scroll.
I've played around with z indexes, bringing the textfield and autocomplete views to the front of super, which doesn't make any difference.
I've also tried setting EnableUserInteraction = NO on the tableview after the autocomplete is triggered, which only has the effect of making the scrollview unresponsive even though its own property of EnableUserInteraction is still set to YES.
I'm thinking that because I also use TPKeyboardAvoiding in my project, that it is somehow complicating the issue.
See the image of one example (it happens on all my views), in this particular example, the table has a header cell on top, then the following are dynamic cells. You can see in the image the hard black line (between tara and Clagary) that is the physical cutoff of the scrollability. i.e. touch above the line and autocomplete scrolls, touch below and whole table scrolls.
Second picture to further detail working and broken interface.
And this also happens in the dynamic cells, not just header. Here is the next example.
The text was updated successfully, but these errors were encountered: