2006/1/11, Jonathan Koren <[EMAIL PROTECTED]>:
I did something similar, but I don't know if this actually answers your
question, but might be able to do something similar.
I wanted to structure my ondrop callbacks to take both the element that
was dropped and the element that was the target of the drop. Since
scriptaculous requires that ondrop callbacks be passed the element being
dragged as its sole argument, I ended up creating a closure containing
my two argument callback, where the target element was bound. Whenever
I created a new drop target, I then passed set my closure to be the
callback.
--
//
// Ing. Francisco J. Calderón S.
// [EMAIL PROTECTED]
// Usuario de GNU/Linux nº 349529
// Maracay, Venezuela
//
_______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
