Hey Sava, Sava Chankov a écrit : > Hi Cristophe, > thanks for the fast reply! Unfortunately, afterFinish callback won't work for > me, because I'm creating another element with the id of the removed row. Is
I don't understand what you mean. You *must not* create another element with the same ID until after you removed the original one: that would mean two elements with the same ID in your DOM, which is the best way to a multitude of horrendous issues, and goes explicitly against (X)HTML/DOM rules. So your fix lies in NOT using the same ID twice (there are certainly so many ways to achieve your goal besides using duplicate IDs...). > there a way to tell the Effect to execute synchronously? You *do not* want to execute synchronously to the removal. This would just make no sense at all: one operation, the effect, executes over a period of time (default is 1 second); the other operation, the removal, is instantaneous, and would therefore break the effect's processing. If you can't find a way not to use the same IDs, just explain what you're trying to achieve here, and we'll find a fix for you :-) But please, think this over before engaging on a needlessly twisted path. -- Christophe Porteneuve aka TDD [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
