David, Thanks, I think that did the trick. Makes sense: if I'm using Date() objects, the dateTimeFormat property is superfluous at best. All my durations are now rendered as imprecise. I presume that's because I've got 'isDuration': 'true', with the true in quotation marks. I'm guessing this property wants an unquoted value: true, yes?
Sadly, using Date() objects does not seem to have affected appreciably the time necessary for processing 2m + events. I'm going to have to think of something else to make performance acceptable: loading in chunks? exhibit2.0? Let me know if you have any ideas. Thanks to all, Jon On Mon, 6 Aug 2007, David Huynh wrote: > Could you remove > 'dateTimeFormat': 'iso8601', > from the file and see if that helps? > > I think the iso8601 date/time parser doesn't test if it's getting a date. > > David _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
