I have defined in my Storyboard (iPad) a view that contains a UICollectionView
, at the bottom of the view there's also a UIToolbar
.
In the UICollectionView
I have added a UICollectionViewCell
(implemented by an iPadCellCollectionViewCell
class) that contains a another view that is a Core-Plot Graph (a CPTGraphHostingView
class).
I have a class called X that implements the UICollectionViewDelegate
and UICollectionViewDataSource
.
In the class X, I build for each cell of my view (in ViewDidLoad
) the Core-Plot Graph and I have the following code to link the graph to the cell of the UICollectionViewCell
- (UICollectionViewCell *)collectionView:(UICollectionView *)collectionView cellForItemAtIndexPath:(NSIndexPath *)indexPath {
static NSString* cellId = @"ChartCollectionId";
iPadCellCollectionViewCell* cell = [self.theCollectionView dequeueReusableCellWithReuseIdentifier:cellId forIndexPath:indexPath];
MyChart* chart = [_charts objectAtIndex:indexPath.row];
cell.hostingView.hostedGraph = chart.barChart;
return cell;
}
It's working fine, all my Graphs are correctly displayed on the screen. The issue happens when the user scroll the view, then one or several cells become "blank". I really don't understand why.
I have found a workaround, instead of adding the CPTGraphHostingView
in the UICollectionViewCell
in the Interface Builder, I build it myself and the previous code becomes:
- (UICollectionViewCell *)collectionView:(UICollectionView *)collectionView cellForItemAtIndexPath:(NSIndexPath *)indexPath {
static NSString* cellId = @"ChartCollectionId";
iPadCellCollectionViewCell* cell = [self.theCollectionView dequeueReusableCellWithReuseIdentifier:cellId forIndexPath:indexPath];
[cell.contentView addSubview:[_hostingViews objectAtIndex:indexPath.row]];
return cell;
}
With this code everything is working fine. Is there any explanations why it's not working when I'm adding the CPTGraphHostingView
in the UICollectionViewCell
with the IB?
Is it an issue to call "addSubview" each time the method is called? No memory leaks?
I've had a similar issue. I fixed it by forcing a repaint when setFrame:
is called on my custom content. In your case, subclass CPTGraphHostingView
and override this method:
-(void)setFrame:(CGRect)frame {
[super setFrame:frame];
[self setNeedsDisplay]; // force drawRect:
}
Edit: An easier way to refresh cell views when they are reused is to override applyLayoutAttributes:
in iPadCellCollectionViewCell
as follows:
-(void)applyLayoutAttributes:(UICollectionViewLayoutAttributes *)layoutAttributes {
// apply custom attributes...
[self.hostingView setNeedsDisplay]; // force drawRect:
}
Regarding your workaround: there will be more and more subviews in the content view, which probably isn't a good thing. However, if you'd remove any old subview before adding the new one, that should be OK, too.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With