A developer I work with thought I should share this with you. There's a race condition in the Timeline code that can cause frustrating problems. Here's his description...
"The key issue here is a race condition in the Timeline JavaScript library. It's being clever in that it dynamically loads various bits of the library "on-the-fly", but it does so using AJAX, which is asynchronous. What was happening was that the gadget would fully load before AJAX had finished returning and loading the definition of the Timeline object. This means that when the function that when the "onLoad" handler is executing, the Timeline object is still in the process of loading. The solution is to explicitly defer the initialization of the Timeline until after we've confirmed that the object has been defined. This is done by calling setInterval() in the "onLoad" handler for the widget with the function that initializes the Timeline. It will be called every 100ms, and return if the Timeline object is undefined. If defined, it clears the event and initializes." -- You received this message because you are subscribed to the Google Groups "SIMILE Widgets" 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/simile-widgets?hl=en.
