Rails spinoffs - May 2007 - Problem with Sortable's onUpdate

I''ve got a very strange problem with Sortables....on most pages
onUpdate works fine, but on one page I have a Sortable that is created
dynamically, and lives inside another list that is also sortable
itself - this all works fine, and I can use onChange with no problems.
However, the onUpdate event does not fire after some reordering has
taken place.

A snippet of the code is:

for(var i = 0; i < sections.length; i++) {
  Sortable.create(sections[i], {
    tag:''div'',
    dropOnEmpty: true,
    containment:sections,
    only:''a1'',
    handle:''h2'',
    constraint:''false'',
    onChange: function (elem)
    {
      alert(1);
    },
    onUpdate: function (elem) {
      alert(2);
    }
  });
}

In the above example, reordering the Sortable will make it alert 1,
but will not make it alert 2.

Any thoughts on how to solve this?


--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---