Thanks, Christophe and Tom, for taking the time to look into this. I got the same results as Tom when I tried his ideas. For now I'll probably just find some way to hack around it, but if I come up with any kind of real solution to the problem with queueing Grow/Shrink I will certainly let you know. -Jay
On Apr 18, 3:51 pm, Christophe Porteneuve <[EMAIL PROTECTED]> wrote: > Hey Jay, > > Don't have time just now, but know that your issue is specific to the > Grow/Shrink pair, which rely on complex internal Effect.Move-based, > parallel-synchronized execution stuff. > > Just try with another effect, say, Effect.BlindDown. It will work. > I'll try to find time and investigate how Grow/Shrink don't seme to bend > themselves to queues, as this is clearly a bug: they should be queueable. > > -- > Christophe Porteneuve a.k.a. TDD > "[They] did not know it was impossible, so they did it." --Mark Twain > Email: [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 [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 -~----------~----~----~----~------~----~------~--~---
