The pages themselves are very lightweight and will not have any impact on the memory usage. If you are loading very large layouts then you might need to load and remove the views based on the program flow, however start with the simplest implementation possible and only optimize if you actually see any issue (in release mode).
The pages themselves are very lightweight and will not have any impact on the memory usage. If you are loading very large layouts then you might need to load and remove the views based on the program flow, however start with the simplest implementation possible and only optimize if you actually see any issue (in release mode).
Thanks for your reply @Erel. The Layout part is ok. However, when I show a large amount of data (For Example, I have a list of names that contains more than 50,000+ names) and then user goes to next screen, then page that contains 50,000+ names are still open. Does it affect memory or performance issues?
That's true, however it is still considered lazy loading with B4XTable as it doesn't create a view for each item. The memory usage shouldn't be too high.
That's true, however it is still considered lazy loading with B4XTable as it doesn't create a view for each item. The memory usage shouldn't be too high.
Can I able to Close the page or Remove Data from this B4Xtable while the other page is on top and then set data when this page(Page Contains B4XTable with 50000+ records) comes to the top?