I have a lazy-column with a pager to show items using paging-compose 1 alpha 16 (latest).
I have some issues around.
1-> Every time an item is off the screen and back again it comes with a leak on the view like it was loading the entire data.
2-> When an item is updated on DB it changes its position on the list (as expected) but it is not show in the new data.
3-> The new data is only displaying correctly when the item goes out and get back to the screen.
I follow this tutorial to achieve the actual behavior https://medium.com/simform-engineering/list-view-with-pagination-using-jetpack-compose-e131174eac8e
My paging Size is of 50 items and i have leaks even with only 15. The views are simple. They have an image and 2 texts. And i tested without the image as well and still remains the problems.
The problem with the second point was that my text where custom AndroidViews and i was missing the update state parameter. For the other problems i still waiting for help
Related
I have a set of objects that I would like to paginate in a bit of a unconventional way. Some objects have a file attached and some don't. The behavior I would like is for the first set of objects without a file attached to be shown on the first set of pages and then for the objects with a file attached to be displayed on the following pages.
So if objects 1-10 have no attachments, and there are 8 objects viewed per page. I would like page one to have 8, and then page 2 to have only 2 objects, and the arrow to proceed to the next page. The remainder of the pages should paginate normally with the remaining objects with files attached, each with 8 per page.
I've looked at some code here:
How to set different page size for the first page in Kaminari?
This allows custom counts on the first page using padding, but haven't got it working correctly and wondering if there is a better solution.
I've had some testers reporting an intermittent issue on a search page that contains a list.
They say when they have been on the page and navigate to a sub page then return that the list is sometimes scrolled all the way to the bottom of the screen.
I've disabled tensile drag on the list, but I wanted to know if there was any other work-around for this issue?
This has nothing to do with tensile drag. When you navigate from one form to another in the old GUI builder the form is re-created from scratch and re-positioned based on the data.
We try to select the previously selected item but if something in the list changed this might trigger issues.
You can override restoreComponentState in the state machine with a blank implementation to see that this is the cause of this behavior. Assuming that it is you can create a special case for the list instance.
I am working on iOS native app and when trying to read from tableView/tableCells I have a problem getting the updated values. At the first time i enter the page/screen I can see all cells. But , if i create an action that adds another cell to the table view when I try to get the list of cells I see an empty list.
Also, When i change a subelement in that cell I can't see the changed sub element both in inspector and in the code.
I tried switching to a different page and also changing tabs in that page and reread the table/cell and subelements but it didn't help.
I've had this issue before. There is no actual reload elements kind of function that I've seen. However a workaround I've found that works is to simply find an element that exists and it'll reload the elements after it does that.
For example:
yourMethodThatLoadsNewElements();
driver.findElementBy(pathToElementThatExistedBefore);
driver.findElementBy(pathToElementThatWasJustLoaded);
I'm encountering a little problem using a UIPageViewController (a 3 pages walkthrough) :
When I slide to change the current page, when the new page is just displaying, images and texts on it are maybe 50 pixels on the top of their normal position during an half second, and after they recover their normal places.
The shift is pretty little, but it's visible when users are trying it. I tried to remove all constraints but there is always the same problem.
Thanks for your help !
I found the problem : it was the status bar of the device (with the battery icon etc...) which was pushing down elements. So you just have to hide it.
Looked many things up, but never posted before. Here's my situation. Any help would be most appreciated.
I've got a wizard with numerous screens with an associated navigation bar made using CSS. As users click from screen to screen, the navigation reflects the current wizard page the user is on. Each screen has different inputs to be collected. Database reads and writes are required during the render and submission of each page.
Here's the catch. Not every page is required. Only required pages are displayed in the navigation and the required information is stored in the database.
My goal is to reduce the number of database queries by dividing the navigation and remaining input into two separate partials. This way I don't have to render the navigation between each screen eliminating the single query every time between screens.
How would I submit the form of the current screen, render the partial view of the next screen, and yet update the query string to reflect the current partial view as well? This way if the user refreshes the page, they get the current screen.
Sounds like pre-optimization. How do you know you're going to have a problem with your navigation because of the database?
Why not separate out your navigation and output cache it?
If you bound determined to change the url without changing the content you need to use History API and if you need a fall back for browsers that don't support that you can use history.js.