-
Notifications
You must be signed in to change notification settings - Fork 277
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
Reusable issue with UITableView #43
Comments
the detailViewController you provide in 'shouldPresent' get saved in the card instance because otherwise every time the card get opened I should ask for a new detailViewController to be provided. |
That's a great idea. Meanwhile, if you have any sample project on UITableView, Kindly drop here, please. |
I edited the shouldPresent method as follows
Comment out the detailVC private variable and add a fullscreenEnabled variable: Create and setup the contentViewController and DetailViewController on the spot instead of storing as a variable
Proposed Better Solution
|
That seems a good solution, could you open a PR so I can test it out ? :) |
Sure, I'll open one today. I have been using this method and it has been working but the only issue is that I am presenting a Web View (WKWebView) in each Detail View Controller. By utilizing this delegate method, I successfully avoid the Web View somehow becoming stale and not presenting any content like in @53, but it has to reload the page every time the card is reopened which often takes some time. Unfortunately WKWebView does its own caching so not sure how to cache the Web Content and prevent it from reloading each time... |
I would like to thank you for the great work.
When we tap on the card you are creating an instance of DetailViewController along with Chaildviewcontroller. when we come out of that screen, you are keeping the view instance in the stack. kindly tell me the solution for this. I'm attaching my sample project in the attachments. kindly look into it as well.
Thanks in advance.
AppStoreCardView.zip
The text was updated successfully, but these errors were encountered: