cellForRowAtIndexPath is being called for non visible cells also
tableview data source method cellForRowAtIndexPath is being called for the non visible rows also which is creating a problem in pagination in tableview. Did anyone face this issue?
ios uitableview swift4.2
add a comment |
tableview data source method cellForRowAtIndexPath is being called for the non visible rows also which is creating a problem in pagination in tableview. Did anyone face this issue?
ios uitableview swift4.2
Just because it is not visible on your screen doesn't mean it is not visible. What is visible and not visible is decided by your tableView frame. Check your table view frame. Also, elaborate your question with screenshots and code.
– Rakesha Shastri
Nov 20 '18 at 6:38
Use prefetch data source property for pagination.
– Desdenova
Nov 20 '18 at 6:39
add a comment |
tableview data source method cellForRowAtIndexPath is being called for the non visible rows also which is creating a problem in pagination in tableview. Did anyone face this issue?
ios uitableview swift4.2
tableview data source method cellForRowAtIndexPath is being called for the non visible rows also which is creating a problem in pagination in tableview. Did anyone face this issue?
ios uitableview swift4.2
ios uitableview swift4.2
asked Nov 20 '18 at 6:35
S.VS.V
538
538
Just because it is not visible on your screen doesn't mean it is not visible. What is visible and not visible is decided by your tableView frame. Check your table view frame. Also, elaborate your question with screenshots and code.
– Rakesha Shastri
Nov 20 '18 at 6:38
Use prefetch data source property for pagination.
– Desdenova
Nov 20 '18 at 6:39
add a comment |
Just because it is not visible on your screen doesn't mean it is not visible. What is visible and not visible is decided by your tableView frame. Check your table view frame. Also, elaborate your question with screenshots and code.
– Rakesha Shastri
Nov 20 '18 at 6:38
Use prefetch data source property for pagination.
– Desdenova
Nov 20 '18 at 6:39
Just because it is not visible on your screen doesn't mean it is not visible. What is visible and not visible is decided by your tableView frame. Check your table view frame. Also, elaborate your question with screenshots and code.
– Rakesha Shastri
Nov 20 '18 at 6:38
Just because it is not visible on your screen doesn't mean it is not visible. What is visible and not visible is decided by your tableView frame. Check your table view frame. Also, elaborate your question with screenshots and code.
– Rakesha Shastri
Nov 20 '18 at 6:38
Use prefetch data source property for pagination.
– Desdenova
Nov 20 '18 at 6:39
Use prefetch data source property for pagination.
– Desdenova
Nov 20 '18 at 6:39
add a comment |
1 Answer
1
active
oldest
votes
The system calls this method to prepare cells ahead of time, so scrolling is smoother and more responsive. If you want to fetch more data as the user scrolls down/up you should rather implement UITableViewDelegate
method tableView(_:willDisplay:forRowAt:)
- this method is called just before the cell is displayed to the user.
func tableView(_ tableView: UITableView, willDisplay cell: UITableViewCell, forRowAt indexPath: IndexPath) is also getting called for non visible cells
– S.V
Nov 20 '18 at 8:47
Have you set your delegates in viewDidLoad?
– Jay Phillips
Nov 20 '18 at 21:03
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53387510%2fcellforrowatindexpath-is-being-called-for-non-visible-cells-also%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The system calls this method to prepare cells ahead of time, so scrolling is smoother and more responsive. If you want to fetch more data as the user scrolls down/up you should rather implement UITableViewDelegate
method tableView(_:willDisplay:forRowAt:)
- this method is called just before the cell is displayed to the user.
func tableView(_ tableView: UITableView, willDisplay cell: UITableViewCell, forRowAt indexPath: IndexPath) is also getting called for non visible cells
– S.V
Nov 20 '18 at 8:47
Have you set your delegates in viewDidLoad?
– Jay Phillips
Nov 20 '18 at 21:03
add a comment |
The system calls this method to prepare cells ahead of time, so scrolling is smoother and more responsive. If you want to fetch more data as the user scrolls down/up you should rather implement UITableViewDelegate
method tableView(_:willDisplay:forRowAt:)
- this method is called just before the cell is displayed to the user.
func tableView(_ tableView: UITableView, willDisplay cell: UITableViewCell, forRowAt indexPath: IndexPath) is also getting called for non visible cells
– S.V
Nov 20 '18 at 8:47
Have you set your delegates in viewDidLoad?
– Jay Phillips
Nov 20 '18 at 21:03
add a comment |
The system calls this method to prepare cells ahead of time, so scrolling is smoother and more responsive. If you want to fetch more data as the user scrolls down/up you should rather implement UITableViewDelegate
method tableView(_:willDisplay:forRowAt:)
- this method is called just before the cell is displayed to the user.
The system calls this method to prepare cells ahead of time, so scrolling is smoother and more responsive. If you want to fetch more data as the user scrolls down/up you should rather implement UITableViewDelegate
method tableView(_:willDisplay:forRowAt:)
- this method is called just before the cell is displayed to the user.
answered Nov 20 '18 at 6:47
LosiowatyLosiowaty
6,38912038
6,38912038
func tableView(_ tableView: UITableView, willDisplay cell: UITableViewCell, forRowAt indexPath: IndexPath) is also getting called for non visible cells
– S.V
Nov 20 '18 at 8:47
Have you set your delegates in viewDidLoad?
– Jay Phillips
Nov 20 '18 at 21:03
add a comment |
func tableView(_ tableView: UITableView, willDisplay cell: UITableViewCell, forRowAt indexPath: IndexPath) is also getting called for non visible cells
– S.V
Nov 20 '18 at 8:47
Have you set your delegates in viewDidLoad?
– Jay Phillips
Nov 20 '18 at 21:03
func tableView(_ tableView: UITableView, willDisplay cell: UITableViewCell, forRowAt indexPath: IndexPath) is also getting called for non visible cells
– S.V
Nov 20 '18 at 8:47
func tableView(_ tableView: UITableView, willDisplay cell: UITableViewCell, forRowAt indexPath: IndexPath) is also getting called for non visible cells
– S.V
Nov 20 '18 at 8:47
Have you set your delegates in viewDidLoad?
– Jay Phillips
Nov 20 '18 at 21:03
Have you set your delegates in viewDidLoad?
– Jay Phillips
Nov 20 '18 at 21:03
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53387510%2fcellforrowatindexpath-is-being-called-for-non-visible-cells-also%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Just because it is not visible on your screen doesn't mean it is not visible. What is visible and not visible is decided by your tableView frame. Check your table view frame. Also, elaborate your question with screenshots and code.
– Rakesha Shastri
Nov 20 '18 at 6:38
Use prefetch data source property for pagination.
– Desdenova
Nov 20 '18 at 6:39