[cp-patches] Fixing the incorrect work of javax.swing.Timer.getInitialDelay()

[Meskauskas Audrius]

1. The Mauve test indicates the wrong work of 
javax.swing.Timer.getInitialDelay() immediately after calling the 
constructor. Regardless of that was passed to the constructor, 
getInitialDelay() always returns 0.

2. Additional test have shown that, indeed, under specific circumstances 
(the initial delay is not explicitly set) the Timer might fire the first 
event immediately after calling the start() method.

> From the code is seen that the initial delay field is not initialised in 
constructor, leaving it with the default value 0.

Both problems can be fixed by setting this field to the constructor 
parameter value.

Audrius Meskauskas

Timer_2.java.diff
Description: Binary data