Adam,
Sorry for the delay. I found the error in the code where I was trying to parse the start date and end date twice causing an issue. This is fixed in Version 2.5.2 - April 30, 2012
* The time layer(s) visibility before the widget is opened is remembered and re-applied when
the widget is closed.
* Fixed bug when start date and end date is manually specified for the time extent.