Hey! Gareth Evans a écrit : > ghosting:false; and now it is working how I expected...
Yeah, ghosting has issues currently on draggables, which may or may not relate to how it affects Droppable behavior (Sortable uses Droppable internally). I fixed a Draggable+ghosting issue recently, which also relied on improper absolute detection in absolutize, and it's in the trunks now. I kinda remember having run into the same quandary when trying to implement the sort of stuff you're dealing with here. Yet I can see a use for proper hoverclass positioning *and* ghosting, so we'll have to dive into this at some point (we = Scripty author + contribs). > Just an annoying container-height css issue now... and postback, which > will be relatively simple to implement. Hell yeah, postback is just an Ajax.Request in onUpdate. > I'd like a method that didn't require modifications to scriptaculous for > the drop indicator, it's a pain when new versions come out. Totally. You're trying to get the class applied on some stuff *between* the elements you're dropping over, right? Just to provide a placeholder for the to-be-dropped element? I kinda remember having achieved that with <span> placeholders b/w elements that were actually sortable. I'll have to dig further code out. At any rate, this kind of feature has been discussed countless times, in various forms and disguises, on this list. Maybe a smart sifting of the archives could yield useful clues. Still, w/o ghosting you're in the clear just now, aren't you? -- Christophe Porteneuve aka TDD [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
