-
Notifications
You must be signed in to change notification settings - Fork 450
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
AQGridViewCell reuseIdentifier property should not be read-only #19
Comments
Feel free to pretend it's read-write, or to redefine it in the header file (or your subclass's implementation file) for your purposes. Proper IB support is on the roadmap, but not very close right now as I have other priorities. That would be preferable to any attempt to make it piggy-back on UITableViewCell, which implements a lot of UITableView-specific stuff— trust me, I'm a reverse-engineer ;o) |
I trust you :-) |
Closing as resolved. |
Thanks for your brilliant working.I want to know how you resolved this issue,i saw the property reuseidentifer is still readonly. |
Just change the ivar or use Key-Value Coding which does access the ivar for On Jun 29, 2013, at 6:12, yuzhou notifications@github.com wrote: Thank for your brilliant working.I want to know how you resolved this — |
Thanks for your time.I added a contentView in XIB and changed the ivar _reuseIdentifier,it worked. |
Since it's not possible to set the identifier of the cell in Interface Builder, it has to be initialized in
awakeFromNib
. However this is not possible since thereuseIdentifier
property is declared read-only in the@interface
. This prevents me from doing the following in my cell subclass:Note that this property is privately redeclared read-write in the implementation file, which lets
AQGridViewCell
do it in its initialization routines:Of course, I can still do (and indeed I must do):
But that kind of defeats the idea of a property.
Of course, if
AQGridViewCell
was a subclass ofUITableViewCell
, this would be moot as I could set the identifier in IB.The text was updated successfully, but these errors were encountered: