Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI am afraid it is a bit more complicated than images within the view, these views are loaded from the storyboard (As opposed to using nibs and loading them in) and they each have their own view controllers and such that get inited. Also, the use of the uicollectionview, while not absolutely mandatory, is strongly recommended to keep consistent with the rest of the app. Do you think I could set the number of cells to some really high number, then move the contents and all of that to the next cell? (I think I saw that somewhere, but that must have performance issues no?)
      singulars
    2. COEven if its more complex, the principle should be the same, you are shuffling your backing data around when your collection view is in a resting state. I have done this successfully on scrollviews, tableviews, and hierarchies of table views within table views without any issues. If you don't want to mess with your backing data you can pull it into a temp data store and mess with that instead? I've also done the high-number-of-cells thing, but that is just to keep up the illusion while we are live-scrolling through data. It's never going to be infallible.
      singulars
    3. COThanks for your help He Was, The theory here seems sound and should translate ok across to my collectionview. I am going to try and duplicate the first cell after the last and vice versa and and snap into the cells. Once done decelerating ill move the user to the "real" first cell or the "real" last cell depending on direction. Keeping my fingers crossed.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload