Skip to content
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

TKCoverFlowView bringCoverAtIndexToFront crashed application #58

Closed
sfigge opened this issue Feb 6, 2011 · 2 comments
Closed

TKCoverFlowView bringCoverAtIndexToFront crashed application #58

sfigge opened this issue Feb 6, 2011 · 2 comments

Comments

@sfigge
Copy link

sfigge commented Feb 6, 2011

Hi, I experience a problem when calling the

(void) bringCoverAtIndexToFront:(int)index animated:(BOOL)animated

function and index is more than 6 covers away from the cover which is currently on the front. So everything everything works fine as long as only six covers need to to be moved/animated. But if it is more, the following stack trace appears. Any idea?


2011-02-06 12:23:14.948 LebRecipes[21238:207] -[NSNull center]: unrecognized selector sent to instance 0x2a46d68
2011-02-06 12:23:14.949 LebRecipes[21238:207] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull center]: unrecognized selector sent to instance 0x2a46d68'
*** Call stack at first throw:
(
0 CoreFoundation 0x029dcb99 exceptionPreprocess + 185
1 libobjc.A.dylib 0x02b2c40e objc_exception_throw + 47
2 CoreFoundation 0x029de6ab -[NSObject(NSObject) doesNotRecognizeSelector:] + 187
3 CoreFoundation 0x0294e2b6 __forwarding
+ 966
4 CoreFoundation 0x0294de72 _CF_forwarding_prep_0 + 50
5 LebRecipes 0x0004f942 -[TKCoverflowView(hidden) snapToAlbum] + 107
6 LebRecipes 0x00050985 -[TKCoverflowView bringCoverAtIndexToFront:animated:] + 89

Thx

@nickpack
Copy link
Contributor

nickpack commented Feb 7, 2011

I had this myself, for some reason calling self.covers rather than just covers prevented it :)

@devinross
Copy link
Owner

Just committed a fix. Thanks for posting the issue.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants