I think I will have to do some testing to see how it goes. There's no way really to fire an event when creating dom elements is complete. That's why I mentioned some sort of periodical functions that runs and checks if elements are "available" which in turn can fire an event... ahwell..
On Nov 27, 5:20 pm, אריה גלזר <[email protected]> wrote: > i might be mistaken, but DOM creation and injection is synchronous so you > should be able to simply run it in the right order. if its from two > separate parts of he code use an event binding or something of the sort that > will fire when creation is complete > ----------- > אריה גלזר > 052-5348-561 > 5561 > > > > On Fri, Nov 27, 2009 at 17:52, Rolf -nl <[email protected]> wrote: > > I have a JSON object that contains info about simple (div) elements > > which should be created and injected into the page. It also contains > > some configuration settings for styling and effects for each element. > > These settings are send to an fxQueueCommand class thingy. > > > I will have to "wait" untill all elements are injected into the page > > before I start the fx on the elements. In case the fx code can't find > > the element, right? (testing this requires various tests with several > > elements on different machines..) > > > Is the only way to check this some function that is run periodically, > > and fires some event if it can find all elements? > > > Or, is creating dom elements really fast and is a simple delay > > sufficient on the fxQueue.run() method. (this sounds already like it's > > going to fail in IE). > > > The other way is returning a bunch of html already created server side > > that can be injected and a json object with only the fx settings, but > > I thought 100% would be a nice thing to do...
