The onDrop callback takes two arguments, the draggable, and the droppable. This is right out of the box.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francisco Calderon
Sent: Friday, January 13, 2006 7:52 AM
To: [email protected]
Subject: Re: [Rails-spinoffs] divider id of container

 

thanks a lot, thats gave me an idea, see ya!

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
//

The information transmitted in this electronic mail is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers.

_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

Reply via email to