Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have been pulling my hair out over this for days and have found a solution for my situation that may help. In my case I have a collapsing photo layout like in the photos app on the ipad. It shows albums with the photos on top of each other and when you tap an album it expands the photos. So what I have is two separate UICollectionViewLayouts and am toggling between them with <code>[self.collectionView setCollectionViewLayout:myLayout animated:YES]</code> I was having your exact problem with the cells jumping before animation and realized it was the <code>contentOffset</code>. I tried everything with the <code>contentOffset</code> but it still jumped during animation. tyler's solution above worked but it was still messing with the animation.</p> <p>Then I noticed that it happens only when there were a few albums on the screen, not enough to fill the screen. My layout overrides <code>-(CGSize)collectionViewContentSize</code> as recommended. When there are only a few albums the collection view content size is less than the views content size. That's causing the jump when I toggle between the collection layouts.</p> <p>So I set a property on my layouts called minHeight and set it to the collection views parent's height. Then I check the height before I return in <code>-(CGSize)collectionViewContentSize</code> I ensure the height is >= the minimum height.</p> <p>Not a true solution but it's working fine now. I would try setting the <code>contentSize</code> of your collection view to be at least the length of it's containing view.</p> <p><strong>edit:</strong> Manicaesar added an easy workaround if you inherit from UICollectionViewFlowLayout:</p> <pre><code>-(CGSize)collectionViewContentSize { //Workaround CGSize superSize = [super collectionViewContentSize]; CGRect frame = self.collectionView.frame; return CGSizeMake(fmaxf(superSize.width, CGRectGetWidth(frame)), fmaxf(superSize.height, CGRectGetHeight(frame))); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODynamically setting layout on UICollectionView causes inexplicable contentOffset change
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJoris Mans
    1. UStassinari
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODynamically setting layout on UICollectionView causes inexplicable contentOffset change
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI played with this some and came to the conclusion that your workaround is reliable only when the contentSize exactly matches the collectionView's size. So I think it works for non-scrolling collection views.
      singulars
      1. PO
      1. USTimothy Moose
    2. COIt's almost correct, the only thing you seem to need to ensure that the collectionViewContentSize method returns a size that is at least as big as the collection view. My layout is vertically scrolling so I simply ensured that I return a size that is the right width, followed by the max of the calculated size by my layout and the height of the collection view.
      singulars
      1. PO
      1. USrougeExciter
    3. COIn case you inherit from UICollectionViewFlowLayout it is as simple as: - (CGSize)collectionViewContentSize { //Workaround CGSize superSize = [super collectionViewContentSize]; CGRect frame = self.collectionView.frame; return CGSizeMake(fmaxf(superSize.width, CGRectGetWidth(frame)), fmaxf(superSize.height, CGRectGetHeight(frame))); }
      singulars
      1. PO
      1. USmanicaesar
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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