I have a div#timeline which is a Sortable. There are multiple instances of div.clip in a separate div which are each draggable, and when dropped over div#timeline get cloned into #timeline and the Sortable is called again to reset everything. Each cloned .clip can be trimmed (this is a video editor) by changing its start and end timecode, and the resulting width is calculated and set. All of this works just great. The Sortable float model is a nice fit for the constraints of the real-world problem.
Now, my client would like to be able to drag still photos over the top of this timeline, and drop them to individual movie clips. Each movie clip could accept multiple photos. Ideally, these photos could be dragged to set their timecode position relative to the parent movie clip, although that's not my problem at the moment. I'm still stuck at getting each div.clip (which is a child of a Sortable) to accept a drop from a separate draggable. I've tried adding each div.clip to the Droppables with Droppables.add as it's cloned into place, but while that seems to work (the classname is modified when you hover over it as though it will accept the drop) when you do try to drop a div.photo onto it, nothing happens. I've tried various combinations of greedy:false on the elements, to no avail. I also tried using the tree:true, treeTag:'div' parameters, and got nothing but a mess. Is there some rule that I'm violating here? Can you nest droppables to this degree with any success? Thanks in advance, Walter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
