DateProvider observers are updated twice for each time step
Issue #49
resolved
The first update appears to be from the time controller action, the second update is from the DatePicker.setDate.
Comments (4)
-
reporter
-
reporter
-
assigned issue to
Bruce Schubert
-
assigned issue to
-
reporter
- changed status to open
I have a workaround for this issue.
-
reporter
- changed status to resolved
Time: Added workaround to prevent recursive DateProvider updates. Resolves
#49. - Added a simple semiphore to signal when we're processing a DateProvider update message.→ <<cset 0f1d0289ef16>>
- Log in to comment
The DateTimeBand is the observer that invokes the DatePicker.setDate. It runs setDate in a separate thread. Not only is this a duplicate update, but the second update is out of sequence with the first due to the "runLater" execution.