My problem, while related to dropOnEmpty as well seems to only occur when my sortables are nested, which is why I can't replicate it on my test page. I've been meaning to update my test page to prove it so I have a clean page to debug from within, that I can post up (it's really hard to post up an internal [read:burried] page of a web application. I think there might be issues in the dropOnEmpty code.
Perhaps we should team up to debug the solution at some point, What Instant Messaging tools do you use? On 6/13/07, junkmate <[EMAIL PROTECTED]> wrote: > > > any update on this? I am having exactly the same problem. > > I have two Div containers, one on top of the other, where you can drag > from on to the other. > Each div is large enough for 5 images to fit on one line. > > With less than 5 images, dragging and dropping is a pleasure, with > everything looking great. However above 5 images in one container > forces the images on to two rows, and then dragging problems start. > The top row is still perfectly fine, but the second row and below it > is very difficult to drag your image where you want it to land, due to > constantly alternating drop positions every pixel you move... > > This problem only occurs with dropOnEmpty set to true, yet I must have > the ability to empty these lists. > > help :D > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
