-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
UICollectionViewCell gets draggable when elements are binded via rx.items(dataSource:) #1081
Closed
5 of 17 tasks
Comments
Hi @ishkawa, I think you can temporarily use Long term solution would require modifying It would probably make sense to make Do you maybe have time to help out with this? |
Yes, I'll try to fix this issue. |
kzaher
added a commit
that referenced
this issue
Feb 12, 2017
kzaher
added a commit
that referenced
this issue
Feb 12, 2017
kzaher
added a commit
that referenced
this issue
Feb 12, 2017
kzaher
added a commit
that referenced
this issue
Feb 19, 2017
Closed
17 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Short description of the issue:
UICollectionViewCell gets draggable when elements are binded via
rx.items(dataSource:)
, even if the delegate does not have implementation ofcollectionView(_:canMoveItemAtIndexPath:)
.Expected outcome:
UICollectionViewCell is not draggable by default.
What actually happens:
UICollectionViewCell is draggable by default.
Self contained code example that reproduces the issue:
Entire project is available here. Run
carthage bootstrap
and openRxCocoaReorderIssue/Demo.xcodeproj
to reproduce the issue.RxSwift/RxCocoa/RxBlocking/RxTest version/commit
3.1.0
Platform/Environment
How easy is to reproduce? (chances of successful reproduce after running the self contained code)
Xcode version:
Installation method:
I have multiple versions of Xcode installed:
(so we can know if this is a potential cause of your issue)
Level of RxSwift knowledge:
(this is so we can understand your level of knowledge
and formulate the response in an appropriate manner)
The text was updated successfully, but these errors were encountered: