It looks as though I ran into this: http://bugs.adobe.com/jira/browse/FLEXDMV-2043
Switching to 3.4 cleared it up, though some of the comments in that bug make me a little nervous about November... On Mon, Mar 15, 2010 at 1:15 PM, Richard Rodseth <[email protected]> wrote: > Wouldn't you know it. A bug showed up today. > > I have a label function for a chart axis that does this: > > return > dateTimeFormatter.format(DateUtils.adjustForTimeZone(labelValue)); > > public static function adjustForTimeZone(d:Date):Date { > // Assumes d is time-zone neutral > // Adjusts by time-zone offset, so that when > // DateFormatter (for example) converts to local, the > // result is the original date. > var offsetms:Number = d.getTimezoneOffset() * > millisecondsPerMinute; > return new Date(d.getTime() + offsetms); > } > > On dates before today, it times out in DateFormatter.format() > > Error: Error #1502: A script has executed for longer than the default > timeout period of 15 seconds. > at mx.formatters::StringFormatter/formatPattern() > at mx.formatters::StringFormatter() > at mx.formatters::DateFormatter/format() > at > com.companyname.admin.clientevents.view::EventExplorerLineChart/dateTimeLabel() > > Error: Error #1502: A script has executed for longer than the default > timeout period of 15 seconds. > at mx.formatters::DateFormatter/format() > at > com.companyname.admin.clientevents.view::EventExplorerLineChart/dateTimeLabel() > at mx.charts::DateTimeAxis/buildLabelCache() > > Anyone else? >
