This repository was archived by the owner on Sep 8, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 438
Items added outside ng-repeat #177
Comments
README clearly states:
And also suggests:
So rephrasing README, I would suggest you to follow one of these directions:
PS1: One more duplicate of #41... |
Sorry for wasting your time - not sure how I missed that. And pretty sure I recall now reading it when I was first trying to get this stuff set up :-/ Thanks for the quick reply. |
NP :) |
tomyam1
added a commit
to tomyam1/ui-sortable
that referenced
this issue
Mar 26, 2015
Fixes angular-ui#41, Fixed angular-ui#177, Fixed angular-ui#98 and Fixes angular-ui#207
tomyam1
added a commit
to tomyam1/ui-sortable
that referenced
this issue
Mar 26, 2015
Fixes angular-ui#41, Fixed angular-ui#177, Fixed angular-ui#98 and Fixes angular-ui#207
tomyam1
added a commit
to tomyam1/ui-sortable
that referenced
this issue
Mar 26, 2015
Fixes angular-ui#41, Fixed angular-ui#177, Fixed angular-ui#98 and Fixes angular-ui#207
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a kind of funny use case where we want to list items (sortable) using ng-repeat, but then add a "footer" item with controls to add items and such. We are trying to use the "items" option and a marker class to accomplish fixing items in place, eg { items: ':not(.pinned)' }
What I'm seeing is that if I add the pinned class via ng-class inside ng-repeat it works as I'd expect - the pinned item cannot be moved : http://codepen.io/anon/pen/Enfte
What I want however is to add a pinned row in my markup outside ng-repeat, eg http://codepen.io/anon/pen/KHlgB
When going this route the last item is draggable, but on drop it snaps into its original position - so the items selector seems to be at least partly effective. It also adds an empty item at the drop position that then remains fixed there (again draggable but not droppable). Subsequent actions do not add additional items.
I am far from an expert on angular so please forgive me if I am doing something stupid here. Just figured I would raise the issue before we start down the road of accomplishing the same visual effect with CSS hackery.
The text was updated successfully, but these errors were encountered: