New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom UITableViewCell or UICollectionViewCell s key archive issue on iOS 6 #8
Comments
I believe I am seeing this exact issue with my code. Do you have any suggestions or examples for how I can manage the archiving mechanism on my custom cell subviews? |
In my app, this issue manifested itself in custom dragging cells not having the correct backgroundColor. You need to make your custom table/collection cells archiveable with initWithCoder. I have a solid example of how to do this, so I'll push it up when I get a chance. |
Excellent. Thanks for the info and thanks in advance for example. |
No worries. Off the top of my head, I think I used the NSCoder passed to initWithCoder to inflate custom properties into the custom table cell subviews then overrode UIView decode* methods to encode the properties. Again, will confirm when I get a chance. |
@dscoleman Finally got round to adding the example, you can find it in the Example dir. |
See my comments on #29 |
Fixed for v2. |
On iOS 6, if you subclass UITableViewCell or UICollectionViewCell and add subviews as properties to your custom cell they are issues with the duplicate dragging cell - the new subviews that you've added are usually not encoded/decoded for the duplicate dragging view. At present you must implement your own archiving mechanism in the subclass for your custom cell subviews.
I will provide examples on how to do this shortly.
The text was updated successfully, but these errors were encountered: