cellForRowAtIndexPath is being called for non visible cells also












0















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?










share|improve this question























  • 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
















0















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?










share|improve this question























  • 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














0












0








0








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?










share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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



















  • 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












1 Answer
1






active

oldest

votes


















0














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.






share|improve this answer
























  • 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











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
});


}
});














draft saved

draft discarded


















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









0














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.






share|improve this answer
























  • 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
















0














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.






share|improve this answer
























  • 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














0












0








0







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.






share|improve this answer













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.







share|improve this answer












share|improve this answer



share|improve this answer










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



















  • 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


















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

How to fix TextFormField cause rebuild widget in Flutter

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith