#67 new
andy k

Draggables.unregister should take an ID argument

Reported by andy k | August 5th, 2008 @ 01:56 PM

If you are creating Draggable objects dynamically (ex: a list of search results where the results can be dragged into another list), and you want to unregister draggable objects when the list changes, you must either have kept a reference to Draggable objects or you must loop through the Draggables.drags array matching element IDs in order to be able unregister.

It would be great if you could call Draggables.unregister(id) as well as Draggables.unregister(draggable).


drags:[] to drags:{}

drags.push(draggable) to drags[draggable.element.id]=draggable

unregister this.drags to

if(drags[draggable]) delete drags[draggable]

else delete drags[draggable.element.id]

Not sure if in that last part about deleting, you'd need to null out the draggable first before deleteing from the drags object.

This assumes that I've understood correctly the role of Draggables.drags and how/why to unregister them.

No comments found

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket