Gareth, I finally found my error.
I have two lists which are filled with an Ajax.Updater() each. The
second Ajax.Updater has a onComplete:function() which calls
Sortable.create("first list") and Sortable.create("second list").
Since the AjaxUpdater() worked asynchronous, I had situations when the
second Ajax.Updater() finished before the first one. This means it's
onComplete function tried to Sortable.create() something, which was
not ready.
I wanted to do all the work in one onComplete() function, because I
have to calculate sums over elements in both sortables.
I changed the first Ajax.Updater() to Ajax.Updater( ... asynchronous:
false, ...) and it works in IE6 and IE7.
Thank you for your support.
On Jun 21, 11:10 am, "Gareth Evans" <[EMAIL PROTECTED]> wrote:
> Ernst, do you have a margin between your sortables?
> I was having the select problem but it actually occurred when i clicked in
> the margin instead of on the sortable
>
> Gareth
>
> On 6/21/07, ernst <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi Thomas,
>
> > sorry about my long delay.
>
> > The slow init is one point. But much worse is the effect, that the
> > sortables do not react on a click. When I try to move a element from
> > one list to another, I am not able to pick up a element and drag it.
> > The only reaction ist the selection of text.
>
> > My sortables contain consists of 2 lists (<ul>) with about 100-150
> > listelements together. The elements themself are small tables with 2
> > rows/3 columns.
>
> > Do you know a upper limit of elements in sortables with drag&drop
> > between different lists?
>
> > Ernst
>
> > On Jun 4, 11:34 am, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
> > > Do you use handles?
>
> > > If so, try the new handles option in Sortable.create, which takes an
> > > array of elements or element ids (of your handles) to speed up
> > > initializing.
>
> > > Basically you can now do:
>
> > > Sortable.create('sortable_elements_handles',{
> > > handle: 'handle',
> > > handles:
> > > ['h_1','h_2','h_3','h_4','h_5','h_6','h_7','h_8','h_9','h_10'],
>
> > > });
>
> > > See test/functional/sortable_test.html (lower half) for more usage
> > > information.
>
> > > Best,
> > > Thomas
>
> > > Am 03.06.2007 um 22:50 schriebernst:
>
> > > > On May 31, 9:15 pm, jdalton <[EMAIL PROTECTED]> wrote:
>
> > > >> Yes it is 1.7.1beta3, but unfortunately I am not able to publish an
> > > >> example online.
> > > >> I was just wondering if other users have had similar problems and
> > > >> found ways around it.
>
> > > > I have the same problem. Maybe I have a litte too much load burdened
> > > > on scriptaculous.
>
> > > > My application has two sortable/dropable lists with nearly 150
> > > > elements in unordered lists. The elements (li) contain a small table
> > > > with an in-place-edit field and are reloaded from the server on
> > > > selection of some other fields.
>
> > > > On Firefox it is fast and usable, in IE I have to wait 5 seconds to
> > > > get the lists on screen. IE seems to be very busy on this, my progress
> > > > indicator (a animated gif) stops the animation.
>
> > > > Even worse I found, that the selection of a draggable element does not
> > > > work on a slower computer, e.g. my laptop on battery power. When I try
> > > > to select e element, I can only select the displayed text. This effect
> > > > is worse in IE7 than IE6.
>
> > > >Ernst
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
