Skip to content
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

Expanded Cells not appearing if another cell is expanded #33

Open
FaridHaddad opened this issue Feb 5, 2018 · 5 comments
Open

Expanded Cells not appearing if another cell is expanded #33

FaridHaddad opened this issue Feb 5, 2018 · 5 comments

Comments

@FaridHaddad
Copy link

I have a tableview with 2 sections. Each section contains only one row (Completed and ongoing orders). Whenever i click on an expandable cell, it opens normally, but if it is expanded, the other one won't expand unless the first one is closed. I debugged it and it is calling the expandedCellsForRowAt and heightsForExpandedRowAt correctly and is returning all the expanded cells that should appear, but they simply won't appear. Can anyone help me please ? Thanks

@Sunnymous
Copy link

Sunnymous commented Feb 8, 2018

@FaridHaddad The only workaround is to put every expandable cells in one section.
If the cells are in the same section, there`s no problem.
The problem only happens when the expandable cells are in different sections and you try to expand them.

@yasirmturk
Copy link

also happens when there is only 1 section
and
most probably in the case when there is only 1 cell expanded under each expandable cell

@swbrenneis
Copy link

The problem is in the ExpandableProcessor insert function. If the newly expanded cells aren't in the same section, the function returns without inserting them. Since the author says he doesn't have time to address issues, I don't see a fix forthcoming. You will need to call closeAll() before returning a new set of cells from expandedCellsForRowAt.

@yasirmturk
Copy link

nvm i use ExpyTableView

@robertogvieira
Copy link
Contributor

@younatics I believe PR #53 fixed the issue discussed here :)

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

No branches or pull requests

5 participants