Hi Bryan, That is really odd behavior bud. I can see how it just stops being a draggable object.
On a different note, that page doesn't work with IE 6. When I click on the "Add a New Page" link, it throws a JS error. Rey... bbuchs wrote: > Hold on, please. I have a use case that your new fix just broke! I appreciate > Stefan's quick response time, but I don't think this was a bug or broken > function. > > I have a list of Draggables, and I can drag these elements onto a Droppable. > When dropped, the callback creates a DOM element and adds it to a Sortable > that's inside the Droppable. Here's a link to a http://beta.bryanbuchs.com/ > demo . > > Now, when I drop one of my draggables into the dropzone, it's no longer a > draggable item (try dragging an item more than once!). This was not the case > before the 11 September 2006 update. I think my case is similar to > Brendan's, but I want to keep my draggables around, not just insert them > into the sortable. > > In both cases, the sortables are not "conflicting" with droppables - they're > different objects. In my opinion, a draggable is a draggable, a droppable is > a droppable, and a sortable is a sortable. if you want to convert an element > from one to the other, it should not happen automatically. If it's an option > that can be passed, that's fine, but it should not be the default behaviour. > > Also, Stefan - can you document the "SortableAddItem" function briefly? > Should the paramater it accepts be a DOM id or a jQuery object? > > > - Bryan > > > > > Stefan Petre wrote: > >>Hi Brendan, >> >>I changed the Sortables. Now you can insert Draggables inside Sortables >>by just dragging them to the list. >> >>Brendan O'Brien wrote: >> >>>Hi all, >>> >>>I have a situation where I want to make a container both Droppable and >>>Sortable at the same time. The use case is, you drag a button into >>>the Droppable container, and when you do so the onDrop callback >>>creates an HTML node and inserts it into the container. I also want >>>those objects to be Sortable, so that I can reorder them after I have >>>dropped them into the container. >>> >>>But if I make the container Droppable first and then Sortable, then it >>>doesn't quite work. When I initialize the containers as Sortable, it >>>first makes the "accept" elements Draggable, and then tries to make >>>the container Droppable. But, since I have already made it Droppable, >>>the Sortable code sees this and skips it. Thus the Droppable still >>>works, and the "accept" elements are draggable, but I can't drop them >>>anywhere, so they always just revert to where they originated from. >>>If I do it the other way around, make the container Sortable and then >>>Droppable then the opposite is true. The elements are sortable, but >>>nothing happens when I drop something in the container. >>> >>>I was wondering if anyone else has seen this problem, and if so if >>>they have a workaround or solution. I tried adding an onDrop as a >>>Sortables configuration parameter, and then appending the method that >>>is passed in after the default onDrop that Sortables adds to the >>>container. That was moderately successful, but then I ran into more >>>issues, because it still tried to sort. I added a cancelling >>>mechanism, but there were more issues with that. You can see where >>>this is going... >>> >>>Any suggestions on this issue would be greatly appreciated. >>> >>>Thanks, >>>Brendan O'Brien >> >> > _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
