-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Angular event not work as documented #319
Comments
I've got the same issue, you can fix it by adding keys in the object in the _emitEvent() function in ng-sortable.js. So the old one (line 80 from ng-sortable.js)
and the new one
.from works great but it seems tha .item is a copy of the item and not the original one |
Fix onAdd event callback to allow evt.item and evt.from.
@yohankoehler Working with DOM elements is not Angular way. |
@RubaXa You are in a directive. |
@yohankoehler So what? Your commit are forwarding DOM elements from directive to outside. |
@RubaXa my bad, sorry please forget this commit !!!. @Raiseupcreativity So I guess you will have to deal with the onRemove event to retrieve the model that the item is comming from. |
@yohankoehler Already forgotten 🙈 |
yes but I've need access on drag-over target, but i've made another directive for that.... |
Hi @RubaXa!
I've tried onAdd event callback but evt.item and evt.from not show up.
http://jsfiddle.net/solitary90/m5jq2wcq/
I'm doing wrong?
(I've already tried dev-branch)
The text was updated successfully, but these errors were encountered: